Skip to content

Commit 15963c8

Browse files
yoshi-automationsofisl
authored andcommitted
fix(serviceconsumermanagement): update the API
#### serviceconsumermanagement:v1beta1 The following keys were changed: - schemas.JavaSettings.properties.libraryPackage.description #### serviceconsumermanagement:v1 The following keys were changed: - schemas.JavaSettings.properties.libraryPackage.description
1 parent ee2b715 commit 15963c8

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

‎discovery/serviceconsumermanagement-v1.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -542,7 +542,7 @@
542542
}
543543
}
544544
},
545-
"revision": "20250227",
545+
"revision": "20250313",
546546
"rootUrl": "https://serviceconsumermanagement.googleapis.com/",
547547
"schemas": {
548548
"AddTenantProjectRequest": {
@@ -1610,7 +1610,7 @@
16101610
"description": "Some settings."
16111611
},
16121612
"libraryPackage": {
1613-
"description": "The package name to use in Java. Clobbers the java_package option set in the protobuf. This should be used **only** by APIs who have already set the language_settings.java.package_name\" field in gapic.yaml. API teams should use the protobuf java_package option where possible. Example of a YAML configuration:: publishing: java_settings: library_package: com.google.cloud.pubsub.v1",
1613+
"description": "The package name to use in Java. Clobbers the java_package option set in the protobuf. This should be used **only** by APIs who have already set the language_settings.java.package_name\" field in gapic.yaml. API teams should use the protobuf java_package option where possible. Example of a YAML configuration:: publishing: library_settings: java_settings: library_package: com.google.cloud.pubsub.v1",
16141614
"type": "string"
16151615
},
16161616
"serviceClassNames": {

‎discovery/serviceconsumermanagement-v1beta1.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -715,7 +715,7 @@
715715
}
716716
}
717717
},
718-
"revision": "20250227",
718+
"revision": "20250313",
719719
"rootUrl": "https://serviceconsumermanagement.googleapis.com/",
720720
"schemas": {
721721
"Api": {
@@ -1695,7 +1695,7 @@
16951695
"description": "Some settings."
16961696
},
16971697
"libraryPackage": {
1698-
"description": "The package name to use in Java. Clobbers the java_package option set in the protobuf. This should be used **only** by APIs who have already set the language_settings.java.package_name\" field in gapic.yaml. API teams should use the protobuf java_package option where possible. Example of a YAML configuration:: publishing: java_settings: library_package: com.google.cloud.pubsub.v1",
1698+
"description": "The package name to use in Java. Clobbers the java_package option set in the protobuf. This should be used **only** by APIs who have already set the language_settings.java.package_name\" field in gapic.yaml. API teams should use the protobuf java_package option where possible. Example of a YAML configuration:: publishing: library_settings: java_settings: library_package: com.google.cloud.pubsub.v1",
16991699
"type": "string"
17001700
},
17011701
"serviceClassNames": {

‎src/apis/serviceconsumermanagement/v1.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -877,7 +877,7 @@ export namespace serviceconsumermanagement_v1 {
877877
*/
878878
common?: Schema$CommonLanguageSettings;
879879
/**
880-
* The package name to use in Java. Clobbers the java_package option set in the protobuf. This should be used **only** by APIs who have already set the language_settings.java.package_name" field in gapic.yaml. API teams should use the protobuf java_package option where possible. Example of a YAML configuration:: publishing: java_settings: library_package: com.google.cloud.pubsub.v1
880+
* The package name to use in Java. Clobbers the java_package option set in the protobuf. This should be used **only** by APIs who have already set the language_settings.java.package_name" field in gapic.yaml. API teams should use the protobuf java_package option where possible. Example of a YAML configuration:: publishing: library_settings: java_settings: library_package: com.google.cloud.pubsub.v1
881881
*/
882882
libraryPackage?: string | null;
883883
/**

‎src/apis/serviceconsumermanagement/v1beta1.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -803,7 +803,7 @@ export namespace serviceconsumermanagement_v1beta1 {
803803
*/
804804
common?: Schema$CommonLanguageSettings;
805805
/**
806-
* The package name to use in Java. Clobbers the java_package option set in the protobuf. This should be used **only** by APIs who have already set the language_settings.java.package_name" field in gapic.yaml. API teams should use the protobuf java_package option where possible. Example of a YAML configuration:: publishing: java_settings: library_package: com.google.cloud.pubsub.v1
806+
* The package name to use in Java. Clobbers the java_package option set in the protobuf. This should be used **only** by APIs who have already set the language_settings.java.package_name" field in gapic.yaml. API teams should use the protobuf java_package option where possible. Example of a YAML configuration:: publishing: library_settings: java_settings: library_package: com.google.cloud.pubsub.v1
807807
*/
808808
libraryPackage?: string | null;
809809
/**

0 commit comments

Comments
 (0)