feat(servicenetworking): update the API

#### servicenetworking:v1beta The following keys were added: - schemas.ConsumerConfig.description - schemas.ConsumerConfig.id - schemas.ConsumerConfig.properties.consumerExportCustomRoutes.description - schemas.ConsumerConfig.properties.consumerExportCustomRoutes.type - schemas.ConsumerConfig.properties.consumerExportSubnetRoutesWithPublicIp.description - schemas.ConsumerConfig.properties.consumerExportSubnetRoutesWithPublicIp.type - schemas.ConsumerConfig.properties.consumerImportCustomRoutes.description - schemas.ConsumerConfig.properties.consumerImportCustomRoutes.type - schemas.ConsumerConfig.properties.consumerImportSubnetRoutesWithPublicIp.description - schemas.ConsumerConfig.properties.consumerImportSubnetRoutesWithPublicIp.type - schemas.ConsumerConfig.properties.producerExportCustomRoutes.description - schemas.ConsumerConfig.properties.producerExportCustomRoutes.type - schemas.ConsumerConfig.properties.producerExportSubnetRoutesWithPublicIp.description - schemas.ConsumerConfig.properties.producerExportSubnetRoutesWithPublicIp.type - schemas.ConsumerConfig.properties.producerImportCustomRoutes.description - schemas.ConsumerConfig.properties.producerImportCustomRoutes.type - schemas.ConsumerConfig.properties.producerImportSubnetRoutesWithPublicIp.description - schemas.ConsumerConfig.properties.producerImportSubnetRoutesWithPublicIp.type - schemas.ConsumerConfig.properties.producerNetwork.description - schemas.ConsumerConfig.properties.producerNetwork.readOnly - schemas.ConsumerConfig.properties.producerNetwork.type - schemas.ConsumerConfig.properties.reservedRanges.description - schemas.ConsumerConfig.properties.reservedRanges.items.type - schemas.ConsumerConfig.properties.reservedRanges.readOnly - schemas.ConsumerConfig.properties.reservedRanges.type - schemas.ConsumerConfig.type - schemas.ConsumerConfigMetadata.description - schemas.ConsumerConfigMetadata.id - schemas.ConsumerConfigMetadata.type The following keys were changed: - schemas.AuthenticationRule.properties.allowWithoutCredential.description - schemas.Context.description - schemas.MetricDescriptor.properties.launchStage.enumDescriptions - schemas.MetricDescriptorMetadata.properties.launchStage.enumDescriptions - schemas.MonitoredResourceDescriptor.properties.launchStage.enumDescriptions - schemas.PolicyBinding.properties.role.description #### servicenetworking:v1 The following keys were added: - schemas.ConsumerConfig.description - schemas.ConsumerConfig.id - schemas.ConsumerConfig.properties.consumerExportCustomRoutes.description - schemas.ConsumerConfig.properties.consumerExportCustomRoutes.type - schemas.ConsumerConfig.properties.consumerExportSubnetRoutesWithPublicIp.description - schemas.ConsumerConfig.properties.consumerExportSubnetRoutesWithPublicIp.type - schemas.ConsumerConfig.properties.consumerImportCustomRoutes.description - schemas.ConsumerConfig.properties.consumerImportCustomRoutes.type - schemas.ConsumerConfig.properties.consumerImportSubnetRoutesWithPublicIp.description - schemas.ConsumerConfig.properties.consumerImportSubnetRoutesWithPublicIp.type - schemas.ConsumerConfig.properties.producerExportCustomRoutes.description - schemas.ConsumerConfig.properties.producerExportCustomRoutes.type - schemas.ConsumerConfig.properties.producerExportSubnetRoutesWithPublicIp.description - schemas.ConsumerConfig.properties.producerExportSubnetRoutesWithPublicIp.type - schemas.ConsumerConfig.properties.producerImportCustomRoutes.description - schemas.ConsumerConfig.properties.producerImportCustomRoutes.type - schemas.ConsumerConfig.properties.producerImportSubnetRoutesWithPublicIp.description - schemas.ConsumerConfig.properties.producerImportSubnetRoutesWithPublicIp.type - schemas.ConsumerConfig.properties.producerNetwork.description - schemas.ConsumerConfig.properties.producerNetwork.readOnly - schemas.ConsumerConfig.properties.producerNetwork.type - schemas.ConsumerConfig.properties.reservedRanges.description - schemas.ConsumerConfig.properties.reservedRanges.items.type - schemas.ConsumerConfig.properties.reservedRanges.readOnly - schemas.ConsumerConfig.properties.reservedRanges.type - schemas.ConsumerConfig.type - schemas.ConsumerConfigMetadata.description - schemas.ConsumerConfigMetadata.id - schemas.ConsumerConfigMetadata.type The following keys were changed: - resources.services.resources.roles.methods.add.description - schemas.AuthenticationRule.properties.allowWithoutCredential.description - schemas.Context.description - schemas.MetricDescriptor.properties.launchStage.enumDescriptions - schemas.MetricDescriptorMetadata.properties.launchStage.enumDescriptions - schemas.MonitoredResourceDescriptor.properties.launchStage.enumDescriptions - schemas.PolicyBinding.properties.role.description
googleapis · Oct 20, 2020 · bd9aae3 · bd9aae3
1 parent bcc1d7e
commit bd9aae3
Show file tree

Hide file tree

Showing 4 changed files with 236 additions and 22 deletions.
diff --git a/discovery/servicenetworking-v1.json b/discovery/servicenetworking-v1.json
@@ -741,7 +741,7 @@
         "roles": {
           "methods": {
             "add": {
-              "description": "Service producers can use this method to add roles in the shared VPC host project. Each role is bound to the provided member. Each role must be selected from within a whitelisted set of roles. Each role is applied at only the granularity specified in the whitelist.",
+              "description": "Service producers can use this method to add roles in the shared VPC host project. Each role is bound to the provided member. Each role must be selected from within an allowlisted set of roles. Each role is applied at only the granularity specified in the allowlist.",
               "flatPath": "v1/services/{servicesId}/roles:add",
               "httpMethod": "POST",
               "id": "servicenetworking.services.roles.add",
@@ -774,7 +774,7 @@
       }
     }
   },
-  "revision": "20201003",
+  "revision": "20201015",
   "rootUrl": "https://servicenetworking.googleapis.com/",
   "schemas": {
     "AddDnsRecordSetMetadata": {
@@ -1050,7 +1050,7 @@
       "id": "AuthenticationRule",
       "properties": {
         "allowWithoutCredential": {
-          "description": "If true, the service accepts API keys without any other credential.",
+          "description": "If true, the service accepts API keys without any other credential. This flag only applies to HTTP and gRPC requests.",
           "type": "boolean"
         },
         "oauth": {
@@ -1206,6 +1206,64 @@
       },
       "type": "object"
     },
+    "ConsumerConfig": {
+      "description": "Configuration information for a private service access connection.",
+      "id": "ConsumerConfig",
+      "properties": {
+        "consumerExportCustomRoutes": {
+          "description": "Export custom routes flag value for peering from consumer to producer.",
+          "type": "boolean"
+        },
+        "consumerExportSubnetRoutesWithPublicIp": {
+          "description": "Export subnet routes with public ip flag value for peering from consumer to producer.",
+          "type": "boolean"
+        },
+        "consumerImportCustomRoutes": {
+          "description": "Import custom routes flag value for peering from consumer to producer.",
+          "type": "boolean"
+        },
+        "consumerImportSubnetRoutesWithPublicIp": {
+          "description": "Import subnet routes with public ip flag value for peering from consumer to producer.",
+          "type": "boolean"
+        },
+        "producerExportCustomRoutes": {
+          "description": "Export custom routes flag value for peering from producer to consumer.",
+          "type": "boolean"
+        },
+        "producerExportSubnetRoutesWithPublicIp": {
+          "description": "Export subnet routes with public ip flag value for peering from producer to consumer.",
+          "type": "boolean"
+        },
+        "producerImportCustomRoutes": {
+          "description": "Import custom routes flag value for peering from producer to consumer.",
+          "type": "boolean"
+        },
+        "producerImportSubnetRoutesWithPublicIp": {
+          "description": "Import subnet routes with public ip flag value for peering from producer to consumer.",
+          "type": "boolean"
+        },
+        "producerNetwork": {
+          "description": "Output only. The VPC host network that is used to host managed service instances. In the format, projects/{project}/global/networks/{network} where {project} is the project number e.g. '12345' and {network} is the network name.",
+          "readOnly": true,
+          "type": "string"
+        },
+        "reservedRanges": {
+          "description": "Output only. The name of the allocated IP address ranges for this private service access connection.",
+          "items": {
+            "type": "string"
+          },
+          "readOnly": true,
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "ConsumerConfigMetadata": {
+      "description": "Metadata provided through GetOperation request for the LRO generated by UpdateConsumerConfig API.",
+      "id": "ConsumerConfigMetadata",
+      "properties": {},
+      "type": "object"
+    },
     "ConsumerProject": {
       "description": "Represents a consumer project.",
       "id": "ConsumerProject",
@@ -1219,7 +1277,7 @@
       "type": "object"
     },
     "Context": {
-      "description": "`Context` defines which contexts an API requests. Example: context: rules: - selector: \"*\" requested: - google.rpc.context.ProjectContext - google.rpc.context.OriginContext The above specifies that all methods in the API request `google.rpc.context.ProjectContext` and `google.rpc.context.OriginContext`. Available context types are defined in package `google.rpc.context`. This also provides mechanism to whitelist any protobuf message extension that can be sent in grpc metadata using “x-goog-ext--bin” and “x-goog-ext--jspb” format. For example, list any service specific protobuf types that can appear in grpc metadata as follows in your yaml file: Example: context: rules: - selector: \"google.example.library.v1.LibraryService.CreateBook\" allowed_request_extensions: - google.foo.v1.NewExtension allowed_response_extensions: - google.foo.v1.NewExtension You can also specify extension ID instead of fully qualified extension name here.",
+      "description": "`Context` defines which contexts an API requests. Example: context: rules: - selector: \"*\" requested: - google.rpc.context.ProjectContext - google.rpc.context.OriginContext The above specifies that all methods in the API request `google.rpc.context.ProjectContext` and `google.rpc.context.OriginContext`. Available context types are defined in package `google.rpc.context`. This also provides mechanism to allowlist any protobuf message extension that can be sent in grpc metadata using “x-goog-ext--bin” and “x-goog-ext--jspb” format. For example, list any service specific protobuf types that can appear in grpc metadata as follows in your yaml file: Example: context: rules: - selector: \"google.example.library.v1.LibraryService.CreateBook\" allowed_request_extensions: - google.foo.v1.NewExtension allowed_response_extensions: - google.foo.v1.NewExtension You can also specify extension ID instead of fully qualified extension name here.",
       "id": "Context",
       "properties": {
         "rules": {
@@ -1997,7 +2055,7 @@
             "The feature is not yet implemented. Users can not use it.",
             "Prelaunch features are hidden from users and are only visible internally.",
             "Early Access features are limited to a closed group of testers. To use these features, you must sign up in advance and sign a Trusted Tester agreement (which includes confidentiality provisions). These features may be unstable, changed in backward-incompatible ways, and are not guaranteed to be released.",
-            "Alpha is a limited availability test for releases before they are cleared for widespread use. By Alpha, all significant design issues are resolved and we are in the process of verifying functionality. Alpha customers need to apply for access, agree to applicable terms, and have their projects whitelisted. Alpha releases don’t have to be feature complete, no SLAs are provided, and there are no technical support obligations, but they will be far enough along that customers can actually use them in test environments or for limited-use tests -- just like they would in normal production cases.",
+            "Alpha is a limited availability test for releases before they are cleared for widespread use. By Alpha, all significant design issues are resolved and we are in the process of verifying functionality. Alpha customers need to apply for access, agree to applicable terms, and have their projects allowlisted. Alpha releases don’t have to be feature complete, no SLAs are provided, and there are no technical support obligations, but they will be far enough along that customers can actually use them in test environments or for limited-use tests -- just like they would in normal production cases.",
             "Beta is the point at which we are ready to open a release for any customer to use. There are no SLA or technical support obligations in a Beta release. Products will be complete from a feature perspective, but may have some open outstanding issues. Beta releases are suitable for limited production use cases.",
             "GA features are open to all developers and are considered stable and fully qualified for production use.",
             "Deprecated features are scheduled to be shut down and removed. For more information, see the “Deprecation Policy” section of our [Terms of Service](https://cloud.google.com/terms/) and the [Google Cloud Platform Subject to the Deprecation Policy](https://cloud.google.com/terms/deprecation) documentation."
@@ -2094,7 +2152,7 @@
             "The feature is not yet implemented. Users can not use it.",
             "Prelaunch features are hidden from users and are only visible internally.",
             "Early Access features are limited to a closed group of testers. To use these features, you must sign up in advance and sign a Trusted Tester agreement (which includes confidentiality provisions). These features may be unstable, changed in backward-incompatible ways, and are not guaranteed to be released.",
-            "Alpha is a limited availability test for releases before they are cleared for widespread use. By Alpha, all significant design issues are resolved and we are in the process of verifying functionality. Alpha customers need to apply for access, agree to applicable terms, and have their projects whitelisted. Alpha releases don’t have to be feature complete, no SLAs are provided, and there are no technical support obligations, but they will be far enough along that customers can actually use them in test environments or for limited-use tests -- just like they would in normal production cases.",
+            "Alpha is a limited availability test for releases before they are cleared for widespread use. By Alpha, all significant design issues are resolved and we are in the process of verifying functionality. Alpha customers need to apply for access, agree to applicable terms, and have their projects allowlisted. Alpha releases don’t have to be feature complete, no SLAs are provided, and there are no technical support obligations, but they will be far enough along that customers can actually use them in test environments or for limited-use tests -- just like they would in normal production cases.",
             "Beta is the point at which we are ready to open a release for any customer to use. There are no SLA or technical support obligations in a Beta release. Products will be complete from a feature perspective, but may have some open outstanding issues. Beta releases are suitable for limited production use cases.",
             "GA features are open to all developers and are considered stable and fully qualified for production use.",
             "Deprecated features are scheduled to be shut down and removed. For more information, see the “Deprecation Policy” section of our [Terms of Service](https://cloud.google.com/terms/) and the [Google Cloud Platform Subject to the Deprecation Policy](https://cloud.google.com/terms/deprecation) documentation."
@@ -2179,7 +2237,7 @@
             "The feature is not yet implemented. Users can not use it.",
             "Prelaunch features are hidden from users and are only visible internally.",
             "Early Access features are limited to a closed group of testers. To use these features, you must sign up in advance and sign a Trusted Tester agreement (which includes confidentiality provisions). These features may be unstable, changed in backward-incompatible ways, and are not guaranteed to be released.",
-            "Alpha is a limited availability test for releases before they are cleared for widespread use. By Alpha, all significant design issues are resolved and we are in the process of verifying functionality. Alpha customers need to apply for access, agree to applicable terms, and have their projects whitelisted. Alpha releases don’t have to be feature complete, no SLAs are provided, and there are no technical support obligations, but they will be far enough along that customers can actually use them in test environments or for limited-use tests -- just like they would in normal production cases.",
+            "Alpha is a limited availability test for releases before they are cleared for widespread use. By Alpha, all significant design issues are resolved and we are in the process of verifying functionality. Alpha customers need to apply for access, agree to applicable terms, and have their projects allowlisted. Alpha releases don’t have to be feature complete, no SLAs are provided, and there are no technical support obligations, but they will be far enough along that customers can actually use them in test environments or for limited-use tests -- just like they would in normal production cases.",
             "Beta is the point at which we are ready to open a release for any customer to use. There are no SLA or technical support obligations in a Beta release. Products will be complete from a feature perspective, but may have some open outstanding issues. Beta releases are suitable for limited production use cases.",
             "GA features are open to all developers and are considered stable and fully qualified for production use.",
             "Deprecated features are scheduled to be shut down and removed. For more information, see the “Deprecation Policy” section of our [Terms of Service](https://cloud.google.com/terms/) and the [Google Cloud Platform Subject to the Deprecation Policy](https://cloud.google.com/terms/deprecation) documentation."
@@ -2353,7 +2411,7 @@
           "type": "string"
         },
         "role": {
-          "description": "Required. Role to apply. Only whitelisted roles can be used at the specified granularity. The role must be one of the following: - 'roles/container.hostServiceAgentUser' applied on the shared VPC host project - 'roles/compute.securityAdmin' applied on the shared VPC host project",
+          "description": "Required. Role to apply. Only allowlisted roles can be used at the specified granularity. The role must be one of the following: - 'roles/container.hostServiceAgentUser' applied on the shared VPC host project - 'roles/compute.securityAdmin' applied on the shared VPC host project",
           "type": "string"
         }
       },