pulumi-gcp-kotlin/com.pulumi.gcp.compute.kotlin.inputs/RegionInstanceTemplateServiceAccountArgsBuilder/scopes

scopes

@JvmName(name = "qhvpxhhjifoojxfw")
suspend fun scopes(value: Output<List<String>>)
@JvmName(name = "otmapnexiqeqtyri")
suspend fun scopes(value: List<String>)

Parameters

value

A list of service scopes. Both OAuth2 URLs and gcloud short names are supported. To allow full access to all Cloud APIs, use the cloud-platform scope. See a complete list of scopes here. The service accounts documentation explains that access scopes are the legacy method of specifying permissions for your instance. To follow best practices you should create a dedicated service account with the minimum permissions the VM requires. To use a dedicated service account this field should be configured as a list containing the cloud-platform scope. See Authenticate workloads using service accounts best practices and Best practices for using service accounts.

@JvmName(name = "drnbghqikvfvgcrg")
suspend fun scopes(vararg values: Output<String>)

@JvmName(name = "ybuueoaogbqhmgvg")
suspend fun scopes(values: List<Output<String>>)
@JvmName(name = "bxwrtibuxsxqnrwd")
suspend fun scopes(vararg values: String)

Parameters

values

A list of service scopes. Both OAuth2 URLs and gcloud short names are supported. To allow full access to all Cloud APIs, use the cloud-platform scope. See a complete list of scopes here. The service accounts documentation explains that access scopes are the legacy method of specifying permissions for your instance. To follow best practices you should create a dedicated service account with the minimum permissions the VM requires. To use a dedicated service account this field should be configured as a list containing the cloud-platform scope. See Authenticate workloads using service accounts best practices and Best practices for using service accounts.