feat(serviceusage): update the api

#### serviceusage:v1

The following keys were added:
- schemas.SelectiveGapicGeneration.properties.generateOmittedAsInternal.type (Total Keys: 1)

#### serviceusage:v1beta1

The following keys were added:
- schemas.SelectiveGapicGeneration.properties.generateOmittedAsInternal.type (Total Keys: 1)

Author: yoshi-automation

docs/dyn/serviceusage_v1.services.html

@@ -244,7 +244,7 @@ <h3>Method Details</h3>
           &quot;overview&quot;: &quot;A String&quot;, # Declares a single overview page. For example: documentation: summary: ... overview: (== include overview.md ==) This is a shortcut for the following declaration (using pages style): documentation: summary: ... pages: - name: Overview content: (== include overview.md ==) Note: you cannot specify both `overview` field and `pages` field.
           &quot;pages&quot;: [ # The top level pages for the documentation set.
             { # Represents a documentation page. A page can contain subpages to represent nested documentation set structure.
-              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
+              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
               &quot;name&quot;: &quot;A String&quot;, # The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`.
               &quot;subpages&quot;: [ # Subpages of this page. The order of subpages specified here will be honored in the generated docset.
                 # Object with schema name: Page
@@ -261,7 +261,7 @@ <h3>Method Details</h3>
           ],
           &quot;sectionOverrides&quot;: [ # Specifies section and content to override boilerplate content provided by go/api-docgen. Currently overrides following sections: 1. rest.service.client_libraries
             { # Represents a documentation page. A page can contain subpages to represent nested documentation set structure.
-              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
+              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
               &quot;name&quot;: &quot;A String&quot;, # The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`.
               &quot;subpages&quot;: [ # Subpages of this page. The order of subpages specified here will be honored in the generated docset.
                 # Object with schema name: Page
@@ -552,7 +552,7 @@ <h3>Method Details</h3>
       &quot;overview&quot;: &quot;A String&quot;, # Declares a single overview page. For example: documentation: summary: ... overview: (== include overview.md ==) This is a shortcut for the following declaration (using pages style): documentation: summary: ... pages: - name: Overview content: (== include overview.md ==) Note: you cannot specify both `overview` field and `pages` field.
       &quot;pages&quot;: [ # The top level pages for the documentation set.
         { # Represents a documentation page. A page can contain subpages to represent nested documentation set structure.
-          &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
+          &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
           &quot;name&quot;: &quot;A String&quot;, # The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`.
           &quot;subpages&quot;: [ # Subpages of this page. The order of subpages specified here will be honored in the generated docset.
             # Object with schema name: Page
@@ -569,7 +569,7 @@ <h3>Method Details</h3>
       ],
       &quot;sectionOverrides&quot;: [ # Specifies section and content to override boilerplate content provided by go/api-docgen. Currently overrides following sections: 1. rest.service.client_libraries
         { # Represents a documentation page. A page can contain subpages to represent nested documentation set structure.
-          &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
+          &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
           &quot;name&quot;: &quot;A String&quot;, # The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`.
           &quot;subpages&quot;: [ # Subpages of this page. The order of subpages specified here will be honored in the generated docset.
             # Object with schema name: Page
@@ -775,7 +775,7 @@ <h3>Method Details</h3>
           &quot;overview&quot;: &quot;A String&quot;, # Declares a single overview page. For example: documentation: summary: ... overview: (== include overview.md ==) This is a shortcut for the following declaration (using pages style): documentation: summary: ... pages: - name: Overview content: (== include overview.md ==) Note: you cannot specify both `overview` field and `pages` field.
           &quot;pages&quot;: [ # The top level pages for the documentation set.
             { # Represents a documentation page. A page can contain subpages to represent nested documentation set structure.
-              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
+              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
               &quot;name&quot;: &quot;A String&quot;, # The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`.
               &quot;subpages&quot;: [ # Subpages of this page. The order of subpages specified here will be honored in the generated docset.
                 # Object with schema name: Page
@@ -792,7 +792,7 @@ <h3>Method Details</h3>
           ],
           &quot;sectionOverrides&quot;: [ # Specifies section and content to override boilerplate content provided by go/api-docgen. Currently overrides following sections: 1. rest.service.client_libraries
             { # Represents a documentation page. A page can contain subpages to represent nested documentation set structure.
-              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
+              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
               &quot;name&quot;: &quot;A String&quot;, # The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`.
               &quot;subpages&quot;: [ # Subpages of this page. The order of subpages specified here will be honored in the generated docset.
                 # Object with schema name: Page

docs/dyn/serviceusage_v1beta1.services.html

@@ -368,7 +368,7 @@ <h3>Method Details</h3>
       &quot;overview&quot;: &quot;A String&quot;, # Declares a single overview page. For example: documentation: summary: ... overview: (== include overview.md ==) This is a shortcut for the following declaration (using pages style): documentation: summary: ... pages: - name: Overview content: (== include overview.md ==) Note: you cannot specify both `overview` field and `pages` field.
       &quot;pages&quot;: [ # The top level pages for the documentation set.
         { # Represents a documentation page. A page can contain subpages to represent nested documentation set structure.
-          &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
+          &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
           &quot;name&quot;: &quot;A String&quot;, # The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`.
           &quot;subpages&quot;: [ # Subpages of this page. The order of subpages specified here will be honored in the generated docset.
             # Object with schema name: Page
@@ -385,7 +385,7 @@ <h3>Method Details</h3>
       ],
       &quot;sectionOverrides&quot;: [ # Specifies section and content to override boilerplate content provided by go/api-docgen. Currently overrides following sections: 1. rest.service.client_libraries
         { # Represents a documentation page. A page can contain subpages to represent nested documentation set structure.
-          &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
+          &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
           &quot;name&quot;: &quot;A String&quot;, # The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`.
           &quot;subpages&quot;: [ # Subpages of this page. The order of subpages specified here will be honored in the generated docset.
             # Object with schema name: Page
@@ -591,7 +591,7 @@ <h3>Method Details</h3>
           &quot;overview&quot;: &quot;A String&quot;, # Declares a single overview page. For example: documentation: summary: ... overview: (== include overview.md ==) This is a shortcut for the following declaration (using pages style): documentation: summary: ... pages: - name: Overview content: (== include overview.md ==) Note: you cannot specify both `overview` field and `pages` field.
           &quot;pages&quot;: [ # The top level pages for the documentation set.
             { # Represents a documentation page. A page can contain subpages to represent nested documentation set structure.
-              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
+              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
               &quot;name&quot;: &quot;A String&quot;, # The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`.
               &quot;subpages&quot;: [ # Subpages of this page. The order of subpages specified here will be honored in the generated docset.
                 # Object with schema name: Page
@@ -608,7 +608,7 @@ <h3>Method Details</h3>
           ],
           &quot;sectionOverrides&quot;: [ # Specifies section and content to override boilerplate content provided by go/api-docgen. Currently overrides following sections: 1. rest.service.client_libraries
             { # Represents a documentation page. A page can contain subpages to represent nested documentation set structure.
-              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
+              &quot;content&quot;: &quot;A String&quot;, # The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.
               &quot;name&quot;: &quot;A String&quot;, # The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`.
               &quot;subpages&quot;: [ # Subpages of this page. The order of subpages specified here will be honored in the generated docset.
                 # Object with schema name: Page

googleapiclient/discovery_cache/documents/serviceusage.v1.json

@@ -426,7 +426,7 @@
 }
 }
 },
-"revision": "20241219",
+"revision": "20250130",
 "rootUrl": "https://serviceusage.googleapis.com/",
 "schemas": {
 "AddEnableRulesMetadata": {
@@ -3065,7 +3065,7 @@
 "id": "Page",
 "properties": {
 "content": {
-"description": "The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.",
+"description": "The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page.",
 "type": "string"
 },
 "name": {
@@ -3338,6 +3338,10 @@
 "description": "This message is used to configure the generation of a subset of the RPCs in a service for client libraries.",
 "id": "SelectiveGapicGeneration",
 "properties": {
+"generateOmittedAsInternal": {
+"description": "Setting this to true indicates to the client generators that methods that would be excluded from the generation should instead be generated in a way that indicates these methods should not be consumed by end users. How this is expressed is up to individual language implementations to decide. Some examples may be: added annotations, obfuscated identifiers, or other language idiomatic patterns.",
+"type": "boolean"
+},
 "methods": {
 "description": "An allowlist of the fully qualified names of RPCs that should be included on public client surfaces.",
 "items": {