pulumi-gcp 8.20.0a1739946722__py3-none-any.whl → 8.20.1__py3-none-any.whl

pulumi_gcp/dataproc/metastore_federation_iam_policy.py

@@ -197,7 +197,7 @@ class MetastoreFederationIamPolicy(pulumi.CustomResource):
                  project: Optional[pulumi.Input[str]] = None,
                  __props__=None):
         """
-        Three different resources help you manage your IAM policy for Dataproc metastore Federation. Each of these resources serves a different use case:
+        Three different resources help you manage your IAM policy for Dataproc Metastore Federation. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreFederationIamPolicy`: Authoritative. Sets the IAM policy for the federation and replaces any existing policy already attached.
         * `dataproc.MetastoreFederationIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the federation are preserved.
@@ -260,8 +260,8 @@ class MetastoreFederationIamPolicy(pulumi.CustomResource):
 
         - 
 
-        # IAM policy for Dataproc metastore Federation
-        Three different resources help you manage your IAM policy for Dataproc metastore Federation. Each of these resources serves a different use case:
+        # IAM policy for Dataproc Metastore Federation
+        Three different resources help you manage your IAM policy for Dataproc Metastore Federation. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreFederationIamPolicy`: Authoritative. Sets the IAM policy for the federation and replaces any existing policy already attached.
         * `dataproc.MetastoreFederationIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the federation are preserved.
@@ -334,7 +334,7 @@ class MetastoreFederationIamPolicy(pulumi.CustomResource):
 
         Any variables not passed in the import command will be taken from the provider configuration.
 
-        Dataproc metastore federation IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc Metastore federation IAM resources can be imported using the resource identifiers, role, and member.
 
         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
 
@@ -376,7 +376,7 @@ class MetastoreFederationIamPolicy(pulumi.CustomResource):
                  args: MetastoreFederationIamPolicyArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        Three different resources help you manage your IAM policy for Dataproc metastore Federation. Each of these resources serves a different use case:
+        Three different resources help you manage your IAM policy for Dataproc Metastore Federation. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreFederationIamPolicy`: Authoritative. Sets the IAM policy for the federation and replaces any existing policy already attached.
         * `dataproc.MetastoreFederationIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the federation are preserved.
@@ -439,8 +439,8 @@ class MetastoreFederationIamPolicy(pulumi.CustomResource):
 
         - 
 
-        # IAM policy for Dataproc metastore Federation
-        Three different resources help you manage your IAM policy for Dataproc metastore Federation. Each of these resources serves a different use case:
+        # IAM policy for Dataproc Metastore Federation
+        Three different resources help you manage your IAM policy for Dataproc Metastore Federation. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreFederationIamPolicy`: Authoritative. Sets the IAM policy for the federation and replaces any existing policy already attached.
         * `dataproc.MetastoreFederationIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the federation are preserved.
@@ -513,7 +513,7 @@ class MetastoreFederationIamPolicy(pulumi.CustomResource):
 
         Any variables not passed in the import command will be taken from the provider configuration.
 
-        Dataproc metastore federation IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc Metastore federation IAM resources can be imported using the resource identifiers, role, and member.
 
         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
 

pulumi_gcp/dataproc/metastore_service.py

@@ -21,7 +21,6 @@ __all__ = ['MetastoreServiceArgs', 'MetastoreService']
 @pulumi.input_type
 class MetastoreServiceArgs:
     def __init__(__self__, *,
-                 service_id: pulumi.Input[str],
                  database_type: Optional[pulumi.Input[str]] = None,
                  deletion_protection: Optional[pulumi.Input[bool]] = None,
                  encryption_config: Optional[pulumi.Input['MetastoreServiceEncryptionConfigArgs']] = None,
@@ -37,16 +36,11 @@ class MetastoreServiceArgs:
                  release_channel: Optional[pulumi.Input[str]] = None,
                  scaling_config: Optional[pulumi.Input['MetastoreServiceScalingConfigArgs']] = None,
                  scheduled_backup: Optional[pulumi.Input['MetastoreServiceScheduledBackupArgs']] = None,
+                 service_id: Optional[pulumi.Input[str]] = None,
                  telemetry_config: Optional[pulumi.Input['MetastoreServiceTelemetryConfigArgs']] = None,
                  tier: Optional[pulumi.Input[str]] = None):
         """
         The set of arguments for constructing a MetastoreService resource.
-        :param pulumi.Input[str] service_id: The ID of the metastore service. The id must contain only letters (a-z, A-Z), numbers (0-9), underscores (_),
-               and hyphens (-). Cannot begin or end with underscore or hyphen. Must consist of between
-               3 and 63 characters.
-               
-               
-               - - -
         :param pulumi.Input[str] database_type: The database type that the Metastore service stores its data.
                Default value is `MYSQL`.
                Possible values are: `MYSQL`, `SPANNER`.
@@ -81,12 +75,17 @@ class MetastoreServiceArgs:
                Structure is documented below.
         :param pulumi.Input['MetastoreServiceScheduledBackupArgs'] scheduled_backup: The configuration of scheduled backup for the metastore service.
                Structure is documented below.
+        :param pulumi.Input[str] service_id: The ID of the metastore service. The id must contain only letters (a-z, A-Z), numbers (0-9), underscores (_),
+               and hyphens (-). Cannot begin or end with underscore or hyphen. Must consist of between
+               3 and 63 characters.
+               
+               
+               - - -
         :param pulumi.Input['MetastoreServiceTelemetryConfigArgs'] telemetry_config: The configuration specifying telemetry settings for the Dataproc Metastore service. If unspecified defaults to JSON.
                Structure is documented below.
         :param pulumi.Input[str] tier: The tier of the service.
                Possible values are: `DEVELOPER`, `ENTERPRISE`.
         """
-        pulumi.set(__self__, "service_id", service_id)
         if database_type is not None:
             pulumi.set(__self__, "database_type", database_type)
         if deletion_protection is not None:
@@ -117,28 +116,13 @@ class MetastoreServiceArgs:
             pulumi.set(__self__, "scaling_config", scaling_config)
         if scheduled_backup is not None:
             pulumi.set(__self__, "scheduled_backup", scheduled_backup)
+        if service_id is not None:
+            pulumi.set(__self__, "service_id", service_id)
         if telemetry_config is not None:
             pulumi.set(__self__, "telemetry_config", telemetry_config)
         if tier is not None:
             pulumi.set(__self__, "tier", tier)
 
-    @property
-    @pulumi.getter(name="serviceId")
-    def service_id(self) -> pulumi.Input[str]:
-        """
-        The ID of the metastore service. The id must contain only letters (a-z, A-Z), numbers (0-9), underscores (_),
-        and hyphens (-). Cannot begin or end with underscore or hyphen. Must consist of between
-        3 and 63 characters.
-
-
-        - - -
-        """
-        return pulumi.get(self, "service_id")
-
-    @service_id.setter
-    def service_id(self, value: pulumi.Input[str]):
-        pulumi.set(self, "service_id", value)
-
     @property
     @pulumi.getter(name="databaseType")
     def database_type(self) -> Optional[pulumi.Input[str]]:
@@ -338,6 +322,23 @@ class MetastoreServiceArgs:
     def scheduled_backup(self, value: Optional[pulumi.Input['MetastoreServiceScheduledBackupArgs']]):
         pulumi.set(self, "scheduled_backup", value)
 
+    @property
+    @pulumi.getter(name="serviceId")
+    def service_id(self) -> Optional[pulumi.Input[str]]:
+        """
+        The ID of the metastore service. The id must contain only letters (a-z, A-Z), numbers (0-9), underscores (_),
+        and hyphens (-). Cannot begin or end with underscore or hyphen. Must consist of between
+        3 and 63 characters.
+
+
+        - - -
+        """
+        return pulumi.get(self, "service_id")
+
+    @service_id.setter
+    def service_id(self, value: Optional[pulumi.Input[str]]):
+        pulumi.set(self, "service_id", value)
+
     @property
     @pulumi.getter(name="telemetryConfig")
     def telemetry_config(self) -> Optional[pulumi.Input['MetastoreServiceTelemetryConfigArgs']]:
@@ -1229,7 +1230,7 @@ class MetastoreService(pulumi.CustomResource):
     @overload
     def __init__(__self__,
                  resource_name: str,
-                 args: MetastoreServiceArgs,
+                 args: Optional[MetastoreServiceArgs] = None,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
         A managed metastore service that serves metadata queries.
@@ -1599,8 +1600,6 @@ class MetastoreService(pulumi.CustomResource):
             __props__.__dict__["release_channel"] = release_channel
             __props__.__dict__["scaling_config"] = scaling_config
             __props__.__dict__["scheduled_backup"] = scheduled_backup
-            if service_id is None and not opts.urn:
-                raise TypeError("Missing required property 'service_id'")
             __props__.__dict__["service_id"] = service_id
             __props__.__dict__["telemetry_config"] = telemetry_config
             __props__.__dict__["tier"] = tier

pulumi_gcp/dataproc/metastore_service_iam_binding.py

@@ -304,7 +304,7 @@ class MetastoreServiceIamBinding(pulumi.CustomResource):
                  service_id: Optional[pulumi.Input[str]] = None,
                  __props__=None):
         """
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -367,8 +367,8 @@ class MetastoreServiceIamBinding(pulumi.CustomResource):
 
         - 
 
-        # IAM policy for Dataproc metastore Service
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        # IAM policy for Dataproc Metastore Service
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -441,7 +441,7 @@ class MetastoreServiceIamBinding(pulumi.CustomResource):
 
         Any variables not passed in the import command will be taken from the provider configuration.
 
-        Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc Metastore service IAM resources can be imported using the resource identifiers, role, and member.
 
         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
 
@@ -496,7 +496,7 @@ class MetastoreServiceIamBinding(pulumi.CustomResource):
                  args: MetastoreServiceIamBindingArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -559,8 +559,8 @@ class MetastoreServiceIamBinding(pulumi.CustomResource):
 
         - 
 
-        # IAM policy for Dataproc metastore Service
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        # IAM policy for Dataproc Metastore Service
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -633,7 +633,7 @@ class MetastoreServiceIamBinding(pulumi.CustomResource):
 
         Any variables not passed in the import command will be taken from the provider configuration.
 
-        Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc Metastore service IAM resources can be imported using the resource identifiers, role, and member.
 
         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
 

pulumi_gcp/dataproc/metastore_service_iam_member.py

@@ -304,7 +304,7 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
                  service_id: Optional[pulumi.Input[str]] = None,
                  __props__=None):
         """
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -367,8 +367,8 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
 
         - 
 
-        # IAM policy for Dataproc metastore Service
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        # IAM policy for Dataproc Metastore Service
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -441,7 +441,7 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
 
         Any variables not passed in the import command will be taken from the provider configuration.
 
-        Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc Metastore service IAM resources can be imported using the resource identifiers, role, and member.
 
         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
 
@@ -496,7 +496,7 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
                  args: MetastoreServiceIamMemberArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -559,8 +559,8 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
 
         - 
 
-        # IAM policy for Dataproc metastore Service
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        # IAM policy for Dataproc Metastore Service
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -633,7 +633,7 @@ class MetastoreServiceIamMember(pulumi.CustomResource):
 
         Any variables not passed in the import command will be taken from the provider configuration.
 
-        Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc Metastore service IAM resources can be imported using the resource identifiers, role, and member.
 
         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
 

pulumi_gcp/dataproc/metastore_service_iam_policy.py

@@ -201,7 +201,7 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
                  service_id: Optional[pulumi.Input[str]] = None,
                  __props__=None):
         """
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -264,8 +264,8 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
 
         - 
 
-        # IAM policy for Dataproc metastore Service
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        # IAM policy for Dataproc Metastore Service
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -338,7 +338,7 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
 
         Any variables not passed in the import command will be taken from the provider configuration.
 
-        Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc Metastore service IAM resources can be imported using the resource identifiers, role, and member.
 
         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.
 
@@ -381,7 +381,7 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
                  args: MetastoreServiceIamPolicyArgs,
                  opts: Optional[pulumi.ResourceOptions] = None):
         """
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -444,8 +444,8 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
 
         - 
 
-        # IAM policy for Dataproc metastore Service
-        Three different resources help you manage your IAM policy for Dataproc metastore Service. Each of these resources serves a different use case:
+        # IAM policy for Dataproc Metastore Service
+        Three different resources help you manage your IAM policy for Dataproc Metastore Service. Each of these resources serves a different use case:
 
         * `dataproc.MetastoreServiceIamPolicy`: Authoritative. Sets the IAM policy for the service and replaces any existing policy already attached.
         * `dataproc.MetastoreServiceIamBinding`: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the service are preserved.
@@ -518,7 +518,7 @@ class MetastoreServiceIamPolicy(pulumi.CustomResource):
 
         Any variables not passed in the import command will be taken from the provider configuration.
 
-        Dataproc metastore service IAM resources can be imported using the resource identifiers, role, and member.
+        Dataproc Metastore service IAM resources can be imported using the resource identifiers, role, and member.
 
         IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g.