Package com.pulumi.gcp.compute.inputs

Class RegionInstanceTemplateServiceAccountArgs.Builder

    • Method Detail

      • email

        public RegionInstanceTemplateServiceAccountArgs.Builder email​(@Nullable
                                                              com.pulumi.core.Output<java.lang.String> email)
        Parameters:
        email - The service account e-mail address. If not given, the default Google Compute Engine service account is used.
        Returns:
        builder

      • email

        public RegionInstanceTemplateServiceAccountArgs.Builder email​(java.lang.String email)
        Parameters:
        email - The service account e-mail address. If not given, the default Google Compute Engine service account is used.
        Returns:
        builder

      • scopes

        public RegionInstanceTemplateServiceAccountArgs.Builder scopes​(com.pulumi.core.Output<java.util.List<java.lang.String>> scopes)
        Parameters:
        scopes - 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](https://cloud.google.com/sdk/gcloud/reference/alpha/compute/instances/set-scopes#--scopes). The [service accounts documentation](https://cloud.google.com/compute/docs/access/service-accounts#accesscopesiam) 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](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances#best_practices) and [Best practices for using service accounts](https://cloud.google.com/iam/docs/best-practices-service-accounts#single-purpose).
        Returns:
        builder

      • scopes

        public RegionInstanceTemplateServiceAccountArgs.Builder scopes​(java.util.List<java.lang.String> scopes)
        Parameters:
        scopes - 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](https://cloud.google.com/sdk/gcloud/reference/alpha/compute/instances/set-scopes#--scopes). The [service accounts documentation](https://cloud.google.com/compute/docs/access/service-accounts#accesscopesiam) 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](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances#best_practices) and [Best practices for using service accounts](https://cloud.google.com/iam/docs/best-practices-service-accounts#single-purpose).
        Returns:
        builder

      • scopes

        public RegionInstanceTemplateServiceAccountArgs.Builder scopes​(java.lang.String... scopes)
        Parameters:
        scopes - 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](https://cloud.google.com/sdk/gcloud/reference/alpha/compute/instances/set-scopes#--scopes). The [service accounts documentation](https://cloud.google.com/compute/docs/access/service-accounts#accesscopesiam) 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](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances#best_practices) and [Best practices for using service accounts](https://cloud.google.com/iam/docs/best-practices-service-accounts#single-purpose).
        Returns:
        builder