google-api-client 0.30.2 → 0.30.3

data/generated/google/apis/dataproc_v1.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://cloud.google.com/dataproc/
     module DataprocV1
       VERSION = 'V1'
-      REVISION = '20190511'
+      REVISION = '20190606'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

data/generated/google/apis/dataproc_v1/classes.rb

@@ -238,6 +238,11 @@ module Google
         # @return [Google::Apis::DataprocV1::InstanceGroupConfig]
         attr_accessor :secondary_worker_config
       
+        # Security related configuration, including Kerberos.
+        # Corresponds to the JSON property `securityConfig`
+        # @return [Google::Apis::DataprocV1::SecurityConfig]
+        attr_accessor :security_config
+      
         # Specifies the selection and config of software inside the cluster.
         # Corresponds to the JSON property `softwareConfig`
         # @return [Google::Apis::DataprocV1::SoftwareConfig]
@@ -261,6 +266,7 @@ module Google
           @initialization_actions = args[:initialization_actions] if args.key?(:initialization_actions)
           @master_config = args[:master_config] if args.key?(:master_config)
           @secondary_worker_config = args[:secondary_worker_config] if args.key?(:secondary_worker_config)
+          @security_config = args[:security_config] if args.key?(:security_config)
           @software_config = args[:software_config] if args.key?(:software_config)
           @worker_config = args[:worker_config] if args.key?(:worker_config)
         end
@@ -1255,6 +1261,120 @@ module Google
         end
       end
       
+      # Specifies Kerberos related configuration.
+      class KerberosConfig
+        include Google::Apis::Core::Hashable
+      
+        # Optional. The admin server (IP or hostname) for the remote trusted realm in a
+        # cross realm trust relationship.
+        # Corresponds to the JSON property `crossRealmTrustAdminServer`
+        # @return [String]
+        attr_accessor :cross_realm_trust_admin_server
+      
+        # Optional. The KDC (IP or hostname) for the remote trusted realm in a cross
+        # realm trust relationship.
+        # Corresponds to the JSON property `crossRealmTrustKdc`
+        # @return [String]
+        attr_accessor :cross_realm_trust_kdc
+      
+        # Optional. The remote realm the Dataproc on-cluster KDC will trust, should the
+        # user enable cross realm trust.
+        # Corresponds to the JSON property `crossRealmTrustRealm`
+        # @return [String]
+        attr_accessor :cross_realm_trust_realm
+      
+        # Optional. The Cloud Storage URI of a KMS encrypted file containing the shared
+        # password between the on-cluster Kerberos realm and the remote trusted realm,
+        # in a cross realm trust relationship.
+        # Corresponds to the JSON property `crossRealmTrustSharedPasswordUri`
+        # @return [String]
+        attr_accessor :cross_realm_trust_shared_password_uri
+      
+        # Optional. Flag to indicate whether to Kerberize the cluster.
+        # Corresponds to the JSON property `enableKerberos`
+        # @return [Boolean]
+        attr_accessor :enable_kerberos
+        alias_method :enable_kerberos?, :enable_kerberos
+      
+        # Optional. The Cloud Storage URI of a KMS encrypted file containing the master
+        # key of the KDC database.
+        # Corresponds to the JSON property `kdcDbKeyUri`
+        # @return [String]
+        attr_accessor :kdc_db_key_uri
+      
+        # Optional. The Cloud Storage URI of a KMS encrypted file containing the
+        # password to the user provided key. For the self-signed certificate, this
+        # password is generated by Dataproc.
+        # Corresponds to the JSON property `keyPasswordUri`
+        # @return [String]
+        attr_accessor :key_password_uri
+      
+        # Optional. The Cloud Storage URI of a KMS encrypted file containing the
+        # password to the user provided keystore. For the self-signed certificate, this
+        # password is generated by Dataproc.
+        # Corresponds to the JSON property `keystorePasswordUri`
+        # @return [String]
+        attr_accessor :keystore_password_uri
+      
+        # Optional. The Cloud Storage URI of the keystore file used for SSL encryption.
+        # If not provided, Dataproc will provide a self-signed certificate.
+        # Corresponds to the JSON property `keystoreUri`
+        # @return [String]
+        attr_accessor :keystore_uri
+      
+        # Required. The uri of the KMS key used to encrypt various sensitive files.
+        # Corresponds to the JSON property `kmsKeyUri`
+        # @return [String]
+        attr_accessor :kms_key_uri
+      
+        # Required. The Cloud Storage URI of a KMS encrypted file containing the root
+        # principal password.
+        # Corresponds to the JSON property `rootPrincipalPasswordUri`
+        # @return [String]
+        attr_accessor :root_principal_password_uri
+      
+        # Optional. The lifetime of the ticket granting ticket, in hours. If not
+        # specified, or user specifies 0, then default value 10 will be used.
+        # Corresponds to the JSON property `tgtLifetimeHours`
+        # @return [Fixnum]
+        attr_accessor :tgt_lifetime_hours
+      
+        # Optional. The Cloud Storage URI of a KMS encrypted file containing the
+        # password to the user provided truststore. For the self-signed certificate,
+        # this password is generated by Dataproc.
+        # Corresponds to the JSON property `truststorePasswordUri`
+        # @return [String]
+        attr_accessor :truststore_password_uri
+      
+        # Optional. The Cloud Storage URI of the truststore file used for SSL encryption.
+        # If not provided, Dataproc will provide a self-signed certificate.
+        # Corresponds to the JSON property `truststoreUri`
+        # @return [String]
+        attr_accessor :truststore_uri
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @cross_realm_trust_admin_server = args[:cross_realm_trust_admin_server] if args.key?(:cross_realm_trust_admin_server)
+          @cross_realm_trust_kdc = args[:cross_realm_trust_kdc] if args.key?(:cross_realm_trust_kdc)
+          @cross_realm_trust_realm = args[:cross_realm_trust_realm] if args.key?(:cross_realm_trust_realm)
+          @cross_realm_trust_shared_password_uri = args[:cross_realm_trust_shared_password_uri] if args.key?(:cross_realm_trust_shared_password_uri)
+          @enable_kerberos = args[:enable_kerberos] if args.key?(:enable_kerberos)
+          @kdc_db_key_uri = args[:kdc_db_key_uri] if args.key?(:kdc_db_key_uri)
+          @key_password_uri = args[:key_password_uri] if args.key?(:key_password_uri)
+          @keystore_password_uri = args[:keystore_password_uri] if args.key?(:keystore_password_uri)
+          @keystore_uri = args[:keystore_uri] if args.key?(:keystore_uri)
+          @kms_key_uri = args[:kms_key_uri] if args.key?(:kms_key_uri)
+          @root_principal_password_uri = args[:root_principal_password_uri] if args.key?(:root_principal_password_uri)
+          @tgt_lifetime_hours = args[:tgt_lifetime_hours] if args.key?(:tgt_lifetime_hours)
+          @truststore_password_uri = args[:truststore_password_uri] if args.key?(:truststore_password_uri)
+          @truststore_uri = args[:truststore_uri] if args.key?(:truststore_uri)
+        end
+      end
+      
       # The list of all clusters in a project.
       class ListClustersResponse
         include Google::Apis::Core::Hashable
@@ -1489,38 +1609,10 @@ module Google
       
         # The Status type defines a logical error model that is suitable for different
         # programming environments, including REST APIs and RPC APIs. It is used by gRPC
-        # (https://github.com/grpc). The error model is designed to be:
-        # Simple to use and understand for most users
-        # Flexible enough to meet unexpected needsOverviewThe Status message contains
-        # three pieces of data: error code, error message, and error details. The error
-        # code should be an enum value of google.rpc.Code, but it may accept additional
-        # error codes if needed. The error message should be a developer-facing English
-        # message that helps developers understand and resolve the error. If a localized
-        # user-facing error message is needed, put the localized message in the error
-        # details or localize it in the client. The optional error details may contain
-        # arbitrary information about the error. There is a predefined set of error
-        # detail types in the package google.rpc that can be used for common error
-        # conditions.Language mappingThe Status message is the logical representation of
-        # the error model, but it is not necessarily the actual wire format. When the
-        # Status message is exposed in different client libraries and different wire
-        # protocols, it can be mapped differently. For example, it will likely be mapped
-        # to some exceptions in Java, but more likely mapped to some error codes in C.
-        # Other usesThe error model and the Status message can be used in a variety of
-        # environments, either with or without APIs, to provide a consistent developer
-        # experience across different environments.Example uses of this error model
-        # include:
-        # Partial errors. If a service needs to return partial errors to the client, it
-        # may embed the Status in the normal response to indicate the partial errors.
-        # Workflow errors. A typical workflow has multiple steps. Each step may have a
-        # Status message for error reporting.
-        # Batch operations. If a client uses batch request and batch response, the
-        # Status message should be used directly inside batch response, one for each
-        # error sub-response.
-        # Asynchronous operations. If an API call embeds asynchronous operation results
-        # in its response, the status of those operations should be represented directly
-        # using the Status message.
-        # Logging. If some API errors are stored in logs, the message Status could be
-        # used directly after any stripping needed for security/privacy reasons.
+        # (https://github.com/grpc). Each Status message contains three pieces of data:
+        # error code, error message, and error details.You can find out more about this
+        # error model and how to work with it in the API Design Guide (https://cloud.
+        # google.com/apis/design/errors).
         # Corresponds to the JSON property `error`
         # @return [Google::Apis::DataprocV1::Status]
         attr_accessor :error
@@ -1943,6 +2035,25 @@ module Google
         end
       end
       
+      # Security related configuration, including Kerberos.
+      class SecurityConfig
+        include Google::Apis::Core::Hashable
+      
+        # Specifies Kerberos related configuration.
+        # Corresponds to the JSON property `kerberosConfig`
+        # @return [Google::Apis::DataprocV1::KerberosConfig]
+        attr_accessor :kerberos_config
+      
+        def initialize(**args)
+           update!(**args)
+        end
+      
+        # Update properties of this object
+        def update!(**args)
+          @kerberos_config = args[:kerberos_config] if args.key?(:kerberos_config)
+        end
+      end
+      
       # Request message for SetIamPolicy method.
       class SetIamPolicyRequest
         include Google::Apis::Core::Hashable
@@ -2168,38 +2279,10 @@ module Google
       
       # The Status type defines a logical error model that is suitable for different
       # programming environments, including REST APIs and RPC APIs. It is used by gRPC
-      # (https://github.com/grpc). The error model is designed to be:
-      # Simple to use and understand for most users
-      # Flexible enough to meet unexpected needsOverviewThe Status message contains
-      # three pieces of data: error code, error message, and error details. The error
-      # code should be an enum value of google.rpc.Code, but it may accept additional
-      # error codes if needed. The error message should be a developer-facing English
-      # message that helps developers understand and resolve the error. If a localized
-      # user-facing error message is needed, put the localized message in the error
-      # details or localize it in the client. The optional error details may contain
-      # arbitrary information about the error. There is a predefined set of error
-      # detail types in the package google.rpc that can be used for common error
-      # conditions.Language mappingThe Status message is the logical representation of
-      # the error model, but it is not necessarily the actual wire format. When the
-      # Status message is exposed in different client libraries and different wire
-      # protocols, it can be mapped differently. For example, it will likely be mapped
-      # to some exceptions in Java, but more likely mapped to some error codes in C.
-      # Other usesThe error model and the Status message can be used in a variety of
-      # environments, either with or without APIs, to provide a consistent developer
-      # experience across different environments.Example uses of this error model
-      # include:
-      # Partial errors. If a service needs to return partial errors to the client, it
-      # may embed the Status in the normal response to indicate the partial errors.
-      # Workflow errors. A typical workflow has multiple steps. Each step may have a
-      # Status message for error reporting.
-      # Batch operations. If a client uses batch request and batch response, the
-      # Status message should be used directly inside batch response, one for each
-      # error sub-response.
-      # Asynchronous operations. If an API call embeds asynchronous operation results
-      # in its response, the status of those operations should be represented directly
-      # using the Status message.
-      # Logging. If some API errors are stored in logs, the message Status could be
-      # used directly after any stripping needed for security/privacy reasons.
+      # (https://github.com/grpc). Each Status message contains three pieces of data:
+      # error code, error message, and error details.You can find out more about this
+      # error model and how to work with it in the API Design Guide (https://cloud.
+      # google.com/apis/design/errors).
       class Status
         include Google::Apis::Core::Hashable
       

data/generated/google/apis/dataproc_v1/representations.rb

@@ -190,6 +190,12 @@ module Google
         include Google::Apis::Core::JsonObjectSupport
       end
       
+      class KerberosConfig
+        class Representation < Google::Apis::Core::JsonRepresentation; end
+      
+        include Google::Apis::Core::JsonObjectSupport
+      end
+      
       class ListClustersResponse
         class Representation < Google::Apis::Core::JsonRepresentation; end
       
@@ -286,6 +292,12 @@ module Google
         include Google::Apis::Core::JsonObjectSupport
       end
       
+      class SecurityConfig
+        class Representation < Google::Apis::Core::JsonRepresentation; end
+      
+        include Google::Apis::Core::JsonObjectSupport
+      end
+      
       class SetIamPolicyRequest
         class Representation < Google::Apis::Core::JsonRepresentation; end
       
@@ -438,6 +450,8 @@ module Google
       
           property :secondary_worker_config, as: 'secondaryWorkerConfig', class: Google::Apis::DataprocV1::InstanceGroupConfig, decorator: Google::Apis::DataprocV1::InstanceGroupConfig::Representation
       
+          property :security_config, as: 'securityConfig', class: Google::Apis::DataprocV1::SecurityConfig, decorator: Google::Apis::DataprocV1::SecurityConfig::Representation
+      
           property :software_config, as: 'softwareConfig', class: Google::Apis::DataprocV1::SoftwareConfig, decorator: Google::Apis::DataprocV1::SoftwareConfig::Representation
       
           property :worker_config, as: 'workerConfig', class: Google::Apis::DataprocV1::InstanceGroupConfig, decorator: Google::Apis::DataprocV1::InstanceGroupConfig::Representation
@@ -692,6 +706,26 @@ module Google
         end
       end
       
+      class KerberosConfig
+        # @private
+        class Representation < Google::Apis::Core::JsonRepresentation
+          property :cross_realm_trust_admin_server, as: 'crossRealmTrustAdminServer'
+          property :cross_realm_trust_kdc, as: 'crossRealmTrustKdc'
+          property :cross_realm_trust_realm, as: 'crossRealmTrustRealm'
+          property :cross_realm_trust_shared_password_uri, as: 'crossRealmTrustSharedPasswordUri'
+          property :enable_kerberos, as: 'enableKerberos'
+          property :kdc_db_key_uri, as: 'kdcDbKeyUri'
+          property :key_password_uri, as: 'keyPasswordUri'
+          property :keystore_password_uri, as: 'keystorePasswordUri'
+          property :keystore_uri, as: 'keystoreUri'
+          property :kms_key_uri, as: 'kmsKeyUri'
+          property :root_principal_password_uri, as: 'rootPrincipalPasswordUri'
+          property :tgt_lifetime_hours, as: 'tgtLifetimeHours'
+          property :truststore_password_uri, as: 'truststorePasswordUri'
+          property :truststore_uri, as: 'truststoreUri'
+        end
+      end
+      
       class ListClustersResponse
         # @private
         class Representation < Google::Apis::Core::JsonRepresentation
@@ -860,6 +894,14 @@ module Google
         end
       end
       
+      class SecurityConfig
+        # @private
+        class Representation < Google::Apis::Core::JsonRepresentation
+          property :kerberos_config, as: 'kerberosConfig', class: Google::Apis::DataprocV1::KerberosConfig, decorator: Google::Apis::DataprocV1::KerberosConfig::Representation
+      
+        end
+      end
+      
       class SetIamPolicyRequest
         # @private
         class Representation < Google::Apis::Core::JsonRepresentation

data/generated/google/apis/dataproc_v1beta2.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://cloud.google.com/dataproc/
     module DataprocV1beta2
       VERSION = 'V1beta2'
-      REVISION = '20190511'
+      REVISION = '20190606'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

data/generated/google/apis/dataproc_v1beta2/classes.rb

@@ -1969,38 +1969,10 @@ module Google
       
         # The Status type defines a logical error model that is suitable for different
         # programming environments, including REST APIs and RPC APIs. It is used by gRPC
-        # (https://github.com/grpc). The error model is designed to be:
-        # Simple to use and understand for most users
-        # Flexible enough to meet unexpected needsOverviewThe Status message contains
-        # three pieces of data: error code, error message, and error details. The error
-        # code should be an enum value of google.rpc.Code, but it may accept additional
-        # error codes if needed. The error message should be a developer-facing English
-        # message that helps developers understand and resolve the error. If a localized
-        # user-facing error message is needed, put the localized message in the error
-        # details or localize it in the client. The optional error details may contain
-        # arbitrary information about the error. There is a predefined set of error
-        # detail types in the package google.rpc that can be used for common error
-        # conditions.Language mappingThe Status message is the logical representation of
-        # the error model, but it is not necessarily the actual wire format. When the
-        # Status message is exposed in different client libraries and different wire
-        # protocols, it can be mapped differently. For example, it will likely be mapped
-        # to some exceptions in Java, but more likely mapped to some error codes in C.
-        # Other usesThe error model and the Status message can be used in a variety of
-        # environments, either with or without APIs, to provide a consistent developer
-        # experience across different environments.Example uses of this error model
-        # include:
-        # Partial errors. If a service needs to return partial errors to the client, it
-        # may embed the Status in the normal response to indicate the partial errors.
-        # Workflow errors. A typical workflow has multiple steps. Each step may have a
-        # Status message for error reporting.
-        # Batch operations. If a client uses batch request and batch response, the
-        # Status message should be used directly inside batch response, one for each
-        # error sub-response.
-        # Asynchronous operations. If an API call embeds asynchronous operation results
-        # in its response, the status of those operations should be represented directly
-        # using the Status message.
-        # Logging. If some API errors are stored in logs, the message Status could be
-        # used directly after any stripping needed for security/privacy reasons.
+        # (https://github.com/grpc). Each Status message contains three pieces of data:
+        # error code, error message, and error details.You can find out more about this
+        # error model and how to work with it in the API Design Guide (https://cloud.
+        # google.com/apis/design/errors).
         # Corresponds to the JSON property `error`
         # @return [Google::Apis::DataprocV1beta2::Status]
         attr_accessor :error
@@ -2818,38 +2790,10 @@ module Google
       
       # The Status type defines a logical error model that is suitable for different
       # programming environments, including REST APIs and RPC APIs. It is used by gRPC
-      # (https://github.com/grpc). The error model is designed to be:
-      # Simple to use and understand for most users
-      # Flexible enough to meet unexpected needsOverviewThe Status message contains
-      # three pieces of data: error code, error message, and error details. The error
-      # code should be an enum value of google.rpc.Code, but it may accept additional
-      # error codes if needed. The error message should be a developer-facing English
-      # message that helps developers understand and resolve the error. If a localized
-      # user-facing error message is needed, put the localized message in the error
-      # details or localize it in the client. The optional error details may contain
-      # arbitrary information about the error. There is a predefined set of error
-      # detail types in the package google.rpc that can be used for common error
-      # conditions.Language mappingThe Status message is the logical representation of
-      # the error model, but it is not necessarily the actual wire format. When the
-      # Status message is exposed in different client libraries and different wire
-      # protocols, it can be mapped differently. For example, it will likely be mapped
-      # to some exceptions in Java, but more likely mapped to some error codes in C.
-      # Other usesThe error model and the Status message can be used in a variety of
-      # environments, either with or without APIs, to provide a consistent developer
-      # experience across different environments.Example uses of this error model
-      # include:
-      # Partial errors. If a service needs to return partial errors to the client, it
-      # may embed the Status in the normal response to indicate the partial errors.
-      # Workflow errors. A typical workflow has multiple steps. Each step may have a
-      # Status message for error reporting.
-      # Batch operations. If a client uses batch request and batch response, the
-      # Status message should be used directly inside batch response, one for each
-      # error sub-response.
-      # Asynchronous operations. If an API call embeds asynchronous operation results
-      # in its response, the status of those operations should be represented directly
-      # using the Status message.
-      # Logging. If some API errors are stored in logs, the message Status could be
-      # used directly after any stripping needed for security/privacy reasons.
+      # (https://github.com/grpc). Each Status message contains three pieces of data:
+      # error code, error message, and error details.You can find out more about this
+      # error model and how to work with it in the API Design Guide (https://cloud.
+      # google.com/apis/design/errors).
       class Status
         include Google::Apis::Core::Hashable
       

data/generated/google/apis/dataproc_v1beta2/service.rb

@@ -185,7 +185,8 @@ module Google
         #   google.com/apis/design/resource_names of the form projects/`project_id`/
         #   regions/`region`
         # @param [Fixnum] page_size
-        #   Optional. The maximum number of results to return in each response.
+        #   Optional. The maximum number of results to return in each response. Must be
+        #   less than or equal to 1000. Defaults to 100.
         # @param [String] page_token
         #   Optional. The page token, returned by a previous call, to request the next
         #   page of results.
@@ -848,7 +849,8 @@ module Google
         #   google.com/apis/design/resource_names of the form projects/`project_id`/
         #   regions/`region`
         # @param [Fixnum] page_size
-        #   Optional. The maximum number of results to return in each response.
+        #   Optional. The maximum number of results to return in each response. Must be
+        #   less than or equal to 1000. Defaults to 100.
         # @param [String] page_token
         #   Optional. The page token, returned by a previous call, to request the next
         #   page of results.