oci-cli 3.69.0__py3-none-any.whl → 3.70.0__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/db/dbnode-snapshot/mount.txt

@@ -0,0 +1,131 @@
+"mount"
+*******
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Mounts the snapshot for the provided dbNode.
+
+
+Usage
+=====
+
+   oci db dbnode-snapshot mount [OPTIONS]
+
+
+Required Parameters
+===================
+
+--db-node-id [text]
+
+The OCID of the Exadata Database Node where snapshot needs to be
+mounted.
+
+--dbnode-snapshot-id [text]
+
+The Exadata Database Node Snapshot OCID.
+
+
+Optional Parameters
+===================
+
+--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 resource to reach the lifecycle state
+defined by "--wait-for-state". Defaults to 1200 seconds.
+
+--wait-for-state [text]
+
+This operation creates, modifies or deletes a resource that has a
+defined lifecycle state. Specify this option to perform the action and
+then wait until the resource reaches a given lifecycle 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:
+
+   AVAILABLE, CREATING, FAILED, MOUNTED, MOUNTING, TERMINATED, TERMINATING, UNMOUNTING
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the resource has
+reached the lifecycle 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 db_node_id=<substitute-value-of-db_node_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/dbnode-snapshot/mount.html#cmdoption-db-node-id
+       export dbnode_snapshot_id=<substitute-value-of-dbnode_snapshot_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/dbnode-snapshot/mount.html#cmdoption-dbnode-snapshot-id
+
+       oci db dbnode-snapshot mount --db-node-id $db_node_id --dbnode-snapshot-id $dbnode_snapshot_id

oci_cli/help_text_producer/data_files/text/cmdref/db/dbnode-snapshot/unmount.txt

@@ -0,0 +1,131 @@
+"unmount"
+*********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Unmounts the snapshot for the provided dbNode.
+
+
+Usage
+=====
+
+   oci db dbnode-snapshot unmount [OPTIONS]
+
+
+Required Parameters
+===================
+
+--db-node-id [text]
+
+The OCID of the Exadata Database Node where snapshot needs to be
+unmounted.
+
+--dbnode-snapshot-id [text]
+
+The Exadata Database Node Snapshot OCID.
+
+
+Optional Parameters
+===================
+
+--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 resource to reach the lifecycle state
+defined by "--wait-for-state". Defaults to 1200 seconds.
+
+--wait-for-state [text]
+
+This operation creates, modifies or deletes a resource that has a
+defined lifecycle state. Specify this option to perform the action and
+then wait until the resource reaches a given lifecycle 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:
+
+   AVAILABLE, CREATING, FAILED, MOUNTED, MOUNTING, TERMINATED, TERMINATING, UNMOUNTING
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the resource has
+reached the lifecycle 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 db_node_id=<substitute-value-of-db_node_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/dbnode-snapshot/unmount.html#cmdoption-db-node-id
+       export dbnode_snapshot_id=<substitute-value-of-dbnode_snapshot_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/dbnode-snapshot/unmount.html#cmdoption-dbnode-snapshot-id
+
+       oci db dbnode-snapshot unmount --db-node-id $db_node_id --dbnode-snapshot-id $dbnode_snapshot_id

oci_cli/help_text_producer/data_files/text/cmdref/db/dbnode-snapshot.txt

@@ -0,0 +1,22 @@
+dbnode-snapshot
+***************
+
+
+Description
+===========
+
+Details of the Database Node Snapshot.
+
+
+Available Commands
+==================
+
+* delete
+
+* get
+
+* list
+
+* mount
+
+* unmount

oci_cli/help_text_producer/data_files/text/cmdref/db/exadb-vm-cluster/add.txt

@@ -0,0 +1,154 @@
+"add"
+*****
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Add a database node snapshots to the Exadb VM cluster..
+
+
+Usage
+=====
+
+   oci db exadb-vm-cluster add [OPTIONS]
+
+
+Required Parameters
+===================
+
+--exadb-vm-cluster-id [text]
+
+The Exadata VM cluster OCID on Exascale Infrastructure.
+
+--name [text]
+
+The user-friendly name for the Database Node Snapshot. The name should
+be unique.
+
+--source-dbnode-ids [complex type]
+
+The OCID of the Exadata Database Node. 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.
+
+
+Optional Parameters
+===================
+
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. For more information, see Resource Tags. 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.
+
+--freeform-tags [complex type]
+
+Free-form tags for this resource. Each tag is a simple key-value pair
+with no predefined name, type, or namespace. For more information, see
+Resource Tags.
+
+Example:
+
+   {"Department": "Finance"}
+
+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.
+
+
+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 and paste the following example into a JSON file, replacing the
+example parameters with your own.
+
+       oci db exadb-vm-cluster add --generate-param-json-input source-dbnode-ids > source-dbnode-ids.json
+
+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 exadb_vm_cluster_id=<substitute-value-of-exadb_vm_cluster_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/exadb-vm-cluster/add.html#cmdoption-exadb-vm-cluster-id
+       export name=<substitute-value-of-name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/exadb-vm-cluster/add.html#cmdoption-name
+
+       oci db exadb-vm-cluster add --exadb-vm-cluster-id $exadb_vm_cluster_id --name $name --source-dbnode-ids file://source-dbnode-ids.json

oci_cli/help_text_producer/data_files/text/cmdref/db/exadb-vm-cluster.txt

@@ -12,6 +12,8 @@ to Exadata Database Service on Exascale Infrastructure only.
 Available Commands
 ==================
 
+* add
+
 * change-compartment
 
 * change-exadb-vm-cluster-subscription

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

@@ -582,6 +582,18 @@ Available Commands
 
   * list-db-system-upgrades
 
+* dbnode-snapshot
+
+  * delete
+
+  * get
+
+  * list
+
+  * mount
+
+  * unmount
+
 * exadata-infrastructure
 
   * activate
@@ -614,6 +626,8 @@ Available Commands
 
 * exadb-vm-cluster
 
+  * add
+
   * change-compartment
 
   * change-exadb-vm-cluster-subscription

oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control/work-request/{work-request-log-entry/list-work-request-logs.txt → work-request-log/list.txt}

@@ -1,5 +1,5 @@
-"list-work-request-logs"
-************************
+"list"
+******
 
 * Description
 
@@ -24,7 +24,7 @@ ID.
 Usage
 =====
 
-   oci delegate-access-control work-request work-request-log-entry list-work-request-logs [OPTIONS]
+   oci delegate-access-control work-request work-request-log list [OPTIONS]
 
 
 Required Parameters
@@ -123,6 +123,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 work_request_id=<substitute-value-of-work_request_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/delegate-access-control/work-request/work-request-log-entry/list-work-request-logs.html#cmdoption-work-request-id
+       export work_request_id=<substitute-value-of-work_request_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/delegate-access-control/work-request/work-request-log/list.html#cmdoption-work-request-id
 
-       oci delegate-access-control work-request work-request-log-entry list-work-request-logs --work-request-id $work_request_id
+       oci delegate-access-control work-request work-request-log list --work-request-id $work_request_id

oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control/work-request.txt

@@ -30,6 +30,6 @@ Available Commands
 
   * list
 
-* work-request-log-entry
+* work-request-log
 
-  * list-work-request-logs
+  * list

oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control.txt

@@ -96,6 +96,6 @@ Available Commands
 
     * list
 
-  * work-request-log-entry
+  * work-request-log
 
-    * list-work-request-logs
+    * list