oci-cli 3.63.2__py3-none-any.whl → 3.64.0__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/ai-vision/vision-private-endpoint/update.txt

@@ -0,0 +1,167 @@
+"update"
+********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Update the visionPrivateEndpoint metadata.
+
+
+Usage
+=====
+
+   oci ai-vision vision-private-endpoint update [OPTIONS]
+
+
+Required Parameters
+===================
+
+--vision-private-endpoint-id [text]
+
+Vision private endpoint Id.
+
+
+Optional Parameters
+===================
+
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. For example: *{“foo-namespace”: {“bar-key”: “value”}}* This
+is a complex type whose value must be valid JSON. The value can be
+provided as a string on the command line or passed in as a file using
+the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
+--description [text]
+
+An optional description of the visionPrivateEndpoint.
+
+--display-name [text]
+
+A human-friendly name for the visionPrivateEndpoint, that can be
+changed.
+
+--force
+
+Perform update without prompting for confirmation.
+
+--freeform-tags [complex type]
+
+A simple key-value pair that is applied without any predefined name,
+type, or scope. It exists for cross-compatibility only. For example:
+*{“bar-key”: “value”}* This is a complex type whose value must be
+valid JSON. The value can be provided as a string on the command line
+or passed in as a file using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
+--from-json [text]
+
+Provide input to this command as a JSON document from a file using the
+file://path-to/file syntax.
+
+The "--generate-full-command-json-input" option can be used to
+generate a sample json file to be used with this command option. The
+key names are pre-populated and match the command option names
+(converted to camelCase format, e.g. compartment-id –> compartmentId),
+while the values of the keys need to be populated by the user before
+using the sample file as an input to this command. For any command
+option that accepts multiple values, the value of the key can be a
+JSON array.
+
+Options can still be provided on the command line. If an option exists
+in both the JSON document and the command line then the command line
+specified value will be used.
+
+For examples on usage of this option, please see our “using CLI with
+advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--if-match [text]
+
+For optimistic concurrency control. In the PUT or DELETE call for a
+resource, set the *if-match* parameter to the value of the etag from a
+previous GET or POST response for that resource. The resource will be
+updated or deleted only if the etag you provide matches the resource’s
+current etag value.
+
+--max-wait-seconds [integer]
+
+The maximum time to wait for the work request to reach the state
+defined by "--wait-for-state". Defaults to 1200 seconds.
+
+--wait-for-state [text]
+
+This operation asynchronously creates, modifies or deletes a resource
+and uses a work request to track the progress of the operation.
+Specify this option to perform the action and then wait until the work
+request reaches a certain state. Multiple states can be specified,
+returning on the first state. For example, "--wait-for-state"
+SUCCEEDED "--wait-for-state" FAILED would return on whichever
+lifecycle state is reached first. If timeout is reached, a return code
+of 2 is returned. For any other error, a return code of 1 is returned.
+
+Accepted values are:
+
+   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, SUCCEEDED, WAITING
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the work request
+has reached the state defined by "--wait-for-state". Defaults to 30
+seconds.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
+
+
+Example using required parameter
+================================
+
+Copy the following CLI commands into a file named example.sh. Run the
+command by typing “bash example.sh” and replacing the example
+parameters with your own.
+
+Please note this sample will only work in the POSIX-compliant bash-
+like shell. You need to set up the OCI configuration and appropriate
+security policies before trying the examples.
+
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/ai-vision/vision-private-endpoint/create.html#cmdoption-compartment-id
+       export subnet_id=<substitute-value-of-subnet_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/ai-vision/vision-private-endpoint/create.html#cmdoption-subnet-id
+
+       vision_private_endpoint_id=$(oci ai-vision vision-private-endpoint create --compartment-id $compartment_id --subnet-id $subnet_id --query data.id --raw-output)
+
+       oci ai-vision vision-private-endpoint update --vision-private-endpoint-id $vision_private_endpoint_id

oci_cli/help_text_producer/data_files/text/cmdref/ai-vision/vision-private-endpoint-collection/list-vision-private-endpoints.txt

@@ -0,0 +1,137 @@
+"list-vision-private-endpoints"
+*******************************
+
+* Description
+
+* Usage
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Returns a list of visionPrivateEndpoints.
+
+
+Usage
+=====
+
+   oci ai-vision vision-private-endpoint-collection list-vision-private-endpoints [OPTIONS]
+
+
+Optional Parameters
+===================
+
+--all
+
+Fetches all pages of results. If you provide this option, then you
+cannot provide the "--limit" option.
+
+--compartment-id, -c [text]
+
+The ID of the compartment in which to list resources.
+
+--display-name [text]
+
+A filter to return only resources that match the entire display name
+given.
+
+--from-json [text]
+
+Provide input to this command as a JSON document from a file using the
+file://path-to/file syntax.
+
+The "--generate-full-command-json-input" option can be used to
+generate a sample json file to be used with this command option. The
+key names are pre-populated and match the command option names
+(converted to camelCase format, e.g. compartment-id –> compartmentId),
+while the values of the keys need to be populated by the user before
+using the sample file as an input to this command. For any command
+option that accepts multiple values, the value of the key can be a
+JSON array.
+
+Options can still be provided on the command line. If an option exists
+in both the JSON document and the command line then the command line
+specified value will be used.
+
+For examples on usage of this option, please see our “using CLI with
+advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--id [text]
+
+The filter to find the device with the given identifier.
+
+--lifecycle-state [text]
+
+The filter to match projects with the given lifecycleState.
+
+Accepted values are:
+
+   ACTIVE, CREATING, DELETED, DELETING, FAILED, UPDATING
+
+--limit [integer]
+
+The maximum number of items to return.
+
+--page [text]
+
+The position at which to start retrieving results. This must come from
+the *opc-next-page* header field of a previous response.
+
+--page-size [integer]
+
+When fetching results, the number of results to fetch per call. Only
+valid when used with "--all" or "--limit", and ignored otherwise.
+
+--sort-by [text]
+
+The field to sort by. Only one sort order may be provided. The default
+order for timeCreated is descending. The default order for displayName
+is ascending.
+
+Accepted values are:
+
+   displayName, timeCreated
+
+--sort-order [text]
+
+The sort order to use, either ‘ASC’ or ‘DESC’.
+
+Accepted values are:
+
+   ASC, DESC
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
+
+
+Example using required parameter
+================================
+
+Copy the following CLI commands into a file named example.sh. Run the
+command by typing “bash example.sh” and replacing the example
+parameters with your own.
+
+Please note this sample will only work in the POSIX-compliant bash-
+like shell. You need to set up the OCI configuration and appropriate
+security policies before trying the examples.
+
+       oci ai-vision vision-private-endpoint-collection list-vision-private-endpoints

oci_cli/help_text_producer/data_files/text/cmdref/ai-vision/vision-private-endpoint-collection.txt

@@ -0,0 +1,14 @@
+vision-private-endpoint-collection
+**********************************
+
+
+Description
+===========
+
+The results of a visionPrivateEndpoint search.
+
+
+Available Commands
+==================
+
+* list-vision-private-endpoints

oci_cli/help_text_producer/data_files/text/cmdref/ai-vision/vision-private-endpoint.txt

@@ -0,0 +1,22 @@
+vision-private-endpoint
+***********************
+
+
+Description
+===========
+
+Vision private endpoint.
+
+
+Available Commands
+==================
+
+* change-compartment
+
+* create
+
+* delete
+
+* get
+
+* update

oci_cli/help_text_producer/data_files/text/cmdref/ai-vision.txt

@@ -80,6 +80,66 @@ Available Commands
 
   * list-projects
 
+* stream-group
+
+  * change-compartment
+
+  * create
+
+  * delete
+
+  * get
+
+  * update
+
+* stream-group-collection
+
+  * list-stream-groups
+
+* stream-job
+
+  * change-compartment
+
+  * create
+
+  * create-stream-job-object-storage-output-location
+
+  * delete
+
+  * get
+
+  * start
+
+  * stop
+
+  * update
+
+  * update-stream-job-object-storage-output-location
+
+* stream-job-collection
+
+  * list-stream-jobs
+
+* stream-source
+
+  * change-compartment
+
+  * create
+
+  * create-stream-source-rtsp-source-details
+
+  * delete
+
+  * get
+
+  * update
+
+  * update-stream-source-rtsp-source-details
+
+* stream-source-collection
+
+  * list-stream-sources
+
 * video-job
 
   * cancel
@@ -90,6 +150,22 @@ Available Commands
 
   * get
 
+* vision-private-endpoint
+
+  * change-compartment
+
+  * create
+
+  * delete
+
+  * get
+
+  * update
+
+* vision-private-endpoint-collection
+
+  * list-vision-private-endpoints
+
 * work-request
 
   * cancel

oci_cli/help_text_producer/data_files/text/cmdref/compute/{compute-gpu-memory-cluster-collection/list-compute-gpu-memory-clusters.txt → compute-gpu-memory-cluster/list.txt}

@@ -1,5 +1,5 @@
-"list-compute-gpu-memory-clusters"
-**********************************
+"list"
+******
 
 * Description
 
@@ -23,7 +23,7 @@ List all of the compute GPU memory clusters.
 Usage
 =====
 
-   oci compute compute-gpu-memory-cluster-collection list-compute-gpu-memory-clusters [OPTIONS]
+   oci compute compute-gpu-memory-cluster list [OPTIONS]
 
 
 Required Parameters
@@ -162,6 +162,6 @@ Please note this sample will only work in the POSIX-compliant bash-
 like shell. You need to set up the OCI configuration and appropriate
 security policies before trying the examples.
 
-       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/compute/compute-gpu-memory-cluster-collection/list-compute-gpu-memory-clusters.html#cmdoption-compartment-id
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/compute/compute-gpu-memory-cluster/list.html#cmdoption-compartment-id
 
-       oci compute compute-gpu-memory-cluster-collection list-compute-gpu-memory-clusters --compartment-id $compartment_id
+       oci compute compute-gpu-memory-cluster list --compartment-id $compartment_id

oci_cli/help_text_producer/data_files/text/cmdref/compute/compute-gpu-memory-cluster.txt

@@ -19,4 +19,6 @@ Available Commands
 
 * get
 
+* list
+
 * update

oci_cli/help_text_producer/data_files/text/cmdref/compute/instance/launch-instance-compute-bare-metal-host-placement-constraint-details.txt

@@ -137,11 +137,6 @@ The OCID of the cluster placement group of the instance.
 
 The OCID of the compute cluster that the instance will be created in.
 
---compute-host-group-id [text]
-
-The OCID of the compute host group attached to the host where the bare
-metal instance will be launched.
-
 --create-vnic-details [complex type]
 
 This is a complex type whose value must be valid JSON. The value can

oci_cli/help_text_producer/data_files/text/cmdref/compute/instance/launch-instance-host-group-placement-constraint-details.txt

@@ -137,11 +137,6 @@ The OCID of the cluster placement group of the instance.
 
 The OCID of the compute cluster that the instance will be created in.
 
---compute-host-group-id [text]
-
-The OCID of the compute host group attached to the host where the bare
-metal instance will be launched.
-
 --create-vnic-details [complex type]
 
 This is a complex type whose value must be valid JSON. The value can

oci_cli/help_text_producer/data_files/text/cmdref/compute/instance/launch.txt

@@ -166,11 +166,6 @@ The OCID of the cluster placement group of the instance.
 
 The OCID of the compute cluster that the instance will be created in.
 
---compute-host-group-id [text]
-
-The OCID of the compute host group attached to the host where the bare
-metal instance will be launched.
-
 --dedicated-vm-host-id [text]
 
 The OCID of the dedicated virtual machine host to place the instance

oci_cli/help_text_producer/data_files/text/cmdref/compute/instance/terminate.txt

@@ -106,6 +106,17 @@ Specifies whether to delete or preserve the data volumes created
 during launch when terminating an instance. When set to *true*, the
 data volumes are preserved. The default value is *true*.
 
+--recycle-level [text]
+
+This optional parameter overrides recycle level for hosts. The
+parameter can be used when hosts are associated with a Capacity
+Reservation. * *FULL_RECYCLE* - Does not skip host wipe. This is the
+default behavior.
+
+Accepted values are:
+
+   FULL_RECYCLE
+
 --wait-for-state [text]
 
 This operation creates, modifies or deletes a resource that has a

oci_cli/help_text_producer/data_files/text/cmdref/compute.txt

@@ -97,11 +97,9 @@ Available Commands
 
   * get
 
-  * update
-
-* compute-gpu-memory-cluster-collection
+  * list
 
-  * list-compute-gpu-memory-clusters
+  * update
 
 * compute-gpu-memory-cluster-instance-summary
 

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/alert-summary/list-alert-analytics.txt

@@ -134,8 +134,8 @@ RFC3339. In SCIM filtering expressions, text, date, and time values
 must be enclosed in quotation marks, with date and time values using
 ISO-8601 format. (Numeric and boolean values should not be quoted.)
 
-**Example:** | query=(timeCreated ge ‘2021-06-04T01-00-26’) and
-(targetNames eq ‘target_1’) query=(featureDetails.userName eq “user”)
+**Example:** | query=(timeCreated ge “2021-06-04T01:00:26.000Z”) and
+(targetNames eq “target_1”) query=(featureDetails.userName eq “user”)
 and (targetNames eq “target_1”) Supported fields: severity status
 alertType targetIds targetNames operationTime lifecycleState
 displayName timeCreated timeUpdated featureDetails.* (* can be any

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/alert-summary/list-alerts.txt

@@ -122,8 +122,8 @@ RFC3339. In SCIM filtering expressions, text, date, and time values
 must be enclosed in quotation marks, with date and time values using
 ISO-8601 format. (Numeric and boolean values should not be quoted.)
 
-**Example:** | query=(timeCreated ge ‘2021-06-04T01-00-26’) and
-(targetNames eq ‘target_1’) query=(featureDetails.userName eq “user”)
+**Example:** | query=(timeCreated ge “2021-06-04T01:00:26.000Z”) and
+(targetNames eq “target_1”) query=(featureDetails.userName eq “user”)
 and (targetNames eq “target_1”) Supported fields: severity status
 alertType targetIds targetNames operationTime lifecycleState
 displayName timeCreated timeUpdated featureDetails.* (* can be any