gcloud: Wed Apr 16 10:41:40 UTC 2025

gcloud/gemini/code-tools-settings/create

@@ -0,0 +1,141 @@
+NAME
+    gcloud gemini code-tools-settings create - create codeToolsSettings
+
+SYNOPSIS
+    gcloud gemini code-tools-settings create
+        (CODE_TOOLS_SETTING : --location=LOCATION)
+        --enabled-tool=[accountConnector=ACCOUNTCONNECTOR],
+          [config=CONFIG],[handle=HANDLE],[tool=TOOL],[uriOverride=URIOVERRIDE]
+        [--labels=[LABELS,...]] [--request-id=REQUEST_ID]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create a codeToolsSetting
+
+EXAMPLES
+    To create the codeToolsSetting, run:
+
+        $ gcloud gemini code-tools-settings create
+
+POSITIONAL ARGUMENTS
+     CodeToolsSetting resource - Identifier. Name of the resource.
+     Format:projects/{project}/locations/{location}/codeToolsSettings/{codeToolsSetting}
+     The arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument code_tools_setting on the command line with a
+        fully specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       CODE_TOOLS_SETTING
+          ID of the codeToolsSetting or fully qualified identifier for the
+          codeToolsSetting.
+
+          To set the code_tools_setting attribute:
+          ▸ provide the argument code_tools_setting on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --location=LOCATION
+          The location id of the codeToolsSetting resource.
+
+          To set the location attribute:
+          ▸ provide the argument code_tools_setting on the command line with
+            a fully specified name;
+          ▸ provide the argument --location on the command line.
+
+REQUIRED FLAGS
+     --enabled-tool=[accountConnector=ACCOUNTCONNECTOR],[config=CONFIG],[handle=HANDLE],[tool=TOOL],[uriOverride=URIOVERRIDE]
+        Required, Represents the full set of enabled tools.
+
+         accountConnector
+            Link to the Dev Connect Account Connector that holds the user
+            credentials.
+            projects/{project}/locations/{location}/accountConnectors/{account_connector_id}.
+
+         config
+            Configuration parameters for the tool.
+
+             key
+                Key of the configuration item.
+
+             value
+                Value of the configuration item.
+
+         handle
+            Handle used to invoke the tool.
+
+         tool
+            Link to the Tool.
+
+         uriOverride
+            Overridden URI, if allowed by Tool.
+
+        Shorthand Example:
+
+            --enabled-tool=accountConnector=string,config=[{key=string,value=string}],handle=string,tool=string,uriOverride=string --enabled-tool=accountConnector=string,config=[{key=string,value=string}],handle=string,tool=string,uriOverride=string
+
+        JSON Example:
+
+            --enabled-tool='[{"accountConnector": "string", "config": [{"key": "string", "value": "string"}], "handle": "string", "tool": "string", "uriOverride": "string"}]'
+
+        File Example:
+
+            --enabled-tool=path_to_file.(yaml|json)
+
+OPTIONAL FLAGS
+     --labels=[LABELS,...]
+        Labels as key value pairs.
+
+         KEY
+            Keys must start with a lowercase character and contain only hyphens
+            (-), underscores (_), lowercase characters, and numbers.
+
+         VALUE
+            Values must contain only hyphens (-), underscores (_), lowercase
+            characters, and numbers.
+
+        Shorthand Example:
+
+            --labels=string=string
+
+        JSON Example:
+
+            --labels='{"string": "string"}'
+
+        File Example:
+
+            --labels=path_to_file.(yaml|json)
+
+     --request-id=REQUEST_ID
+        An optional request ID to identify requests. Specify a unique request
+        ID so that if you must retry your request, the server will know to
+        ignore the request if it has already been completed. The server will
+        guarantee that for at least 60 minutes since the first request.
+
+        For example, consider a situation where you make an initial request and
+        the request times out. If you make the request again with the same
+        request ID, the server can check if original operation with the same
+        request ID was received, and if so, will ignore the second request.
+        This prevents clients from accidentally creating duplicate commitments.
+
+        The request ID must be a valid UUID with the exception that zero UUID
+        is not supported (00000000-0000-0000-0000-000000000000).
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the cloudaicompanion/v1 API. The full documentation for
+    this API can be found at: https://cloud.google.com/gemini