metadata

@JvmName(name = "moohirmvmaddaepg")
suspend fun metadata(value: Output<Map<String, String>>)
@JvmName(name = "gjdsnxhgplnimabw")
suspend fun metadata(value: Map<String, String>?)

Parameters

value

Metadata key/value pairs to make available from within the instance. Ssh keys attached in the Cloud Console will be removed. Add them to your config in order to keep them attached to your instance. A list of default metadata values (e.g. ssh-keys) can be found here

Depending on the OS you choose for your instance, some metadata keys have special functionality. Most linux-based images will run the content of metadata.startup-script in a shell on every boot. At a minimum, Debian, CentOS, RHEL, SLES, Container-Optimized OS, and Ubuntu images support this key. Windows instances require other keys depending on the format of the script and the time you would like it to run - see this table. For the convenience of the users of metadata.startup-script, we provide a special attribute, metadata_startup_script, which is documented below.


@JvmName(name = "akwcqtrurxeioynm")
fun metadata(vararg values: Pair<String, String>)

Parameters

values

Metadata key/value pairs to make available from within the instance. Ssh keys attached in the Cloud Console will be removed. Add them to your config in order to keep them attached to your instance. A list of default metadata values (e.g. ssh-keys) can be found here

Depending on the OS you choose for your instance, some metadata keys have special functionality. Most linux-based images will run the content of metadata.startup-script in a shell on every boot. At a minimum, Debian, CentOS, RHEL, SLES, Container-Optimized OS, and Ubuntu images support this key. Windows instances require other keys depending on the format of the script and the time you would like it to run - see this table. For the convenience of the users of metadata.startup-script, we provide a special attribute, metadata_startup_script, which is documented below.