oci-cli 3.66.1__py3-none-any.whl → 3.67.0__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database.txt

@@ -28,6 +28,8 @@ Available Commands
 * create-autonomous-database-create-cross-region-disaster-recovery-
   details
 
+* create-autonomous-database-gcp-key-details
+
 * create-autonomous-database-undelete-autonomous-database-details
 
 * create-cross-tenancy-disaster-recovery-details
@@ -93,3 +95,5 @@ Available Commands
 * switchover
 
 * update
+
+* update-autonomous-database-gcp-key-details

oci_cli/help_text_producer/data_files/text/cmdref/db/cloud-exa-infra/configure-exascale.txt

@@ -0,0 +1,136 @@
+"configure-exascale"
+********************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Configures Exascale on Cloud exadata infrastructure resource. Applies
+to Exadata Cloud Service instances only.
+
+
+Usage
+=====
+
+   oci db cloud-exa-infra configure-exascale [OPTIONS]
+
+
+Required Parameters
+===================
+
+--cloud-exa-infra-id [text]
+
+The OCID of the cloud Exadata infrastructure.
+
+--total-storage-in-gbs [integer]
+
+Storage size needed for Exascale in GBs.
+
+
+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, FAILED, MAINTENANCE_IN_PROGRESS, PROVISIONING, TERMINATED, TERMINATING, UPDATING
+
+--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 availability_domain=<substitute-value-of-availability_domain> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/cloud-exa-infra/create.html#cmdoption-availability-domain
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/cloud-exa-infra/create.html#cmdoption-compartment-id
+       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/cloud-exa-infra/create.html#cmdoption-display-name
+       export shape=<substitute-value-of-shape> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/cloud-exa-infra/create.html#cmdoption-shape
+       export total_storage_in_gbs=<substitute-value-of-total_storage_in_gbs> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/cloud-exa-infra/configure-exascale.html#cmdoption-total-storage-in-gbs
+
+       cloud_exa_infra_id=$(oci db cloud-exa-infra create --availability-domain $availability_domain --compartment-id $compartment_id --display-name $display_name --shape $shape --query data.id --raw-output)
+
+       oci db cloud-exa-infra configure-exascale --cloud-exa-infra-id $cloud_exa_infra_id --total-storage-in-gbs $total_storage_in_gbs

oci_cli/help_text_producer/data_files/text/cmdref/db/cloud-exa-infra.txt

@@ -18,6 +18,8 @@ Available Commands
 
 * change-compartment
 
+* configure-exascale
+
 * create
 
 * delete

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

@@ -44,16 +44,38 @@ The OCID of the compartment.
 
 --cpu-core-count [integer]
 
-The number of ECPUs (X11M and higher) or number of OCPUs (X10M and
-earlier) to enable for the VM cluster.
+For fixed shapes, this is the total number of OCPUs to enable across
+the VM cluster.
 
-* Exadata.Base.48 - Specify a multiple of 2, from 0 to 48.  -
-  Exadata.Quarter1.84 - Specify a multiple of 2, from 22 to 84.  -
-  Exadata.Half1.168 - Specify a multiple of 4, from 44 to 168.  -
-  Exadata.Full1.336 - Specify a multiple of 8, from 88 to 336.  -
-  Exadata.Quarter2.92 - Specify a multiple of 2, from 0 to 92.  -
-  Exadata.Half2.184 - Specify a multiple of 4, from 0 to 184.  -
-  Exadata.Full2.368 - Specify a multiple of 8, from 0 to 368.
+   * Exadata.Base.48 - Specify a multiple of 2, from 0 to 48.  -
+     Exadata.Quarter3.100 - Specify a multiple of 2, from 0 to 100.  -
+     Exadata.Half3.200 - Specify a multiple of 4, from 0 to 200.  -
+     Exadata.Full3.400 - Specify a multiple of 8, from 0 to 400.
+
+The API specification for fixed shape values is
+https://docs.oracle.com/en-
+us/iaas/api/#/en/database/20160918/DbSystemShapeSummary
+
+   For flexible shapes X8M and X9M, this is the total number of OCPUs
+   to enable across the VM cluster. The number available for the VM
+   cluster will be based on the number of database servers selected
+   for provisioning the VM cluster on the Exadata Infrastructure.
+
+   * Exadata.X8M - Specify a multiple of 2, from 2 to 50 per X8M
+     database server.  - Exadata.X9M - Specify a multiple of 2, from 2
+     to 126 per X9M database server.
+
+For flexible shapes X11M and higher, this is the total number of ECPUs
+to enable across the VM cluster. The number available for the VM
+cluster will be based on the number of database servers selected for
+provisioning the VM cluster on the Exadata Infrastructure.
+
+   * Exadata.X11M - Specify a multiple of 8, from 8 to 760 per X11M
+     database server.
+
+The API specification for flexible shape values is
+https://docs.oracle.com/en-
+us/iaas/api/#/en/database/20160918/datatypes/FlexComponentSummary
 
 --display-name [text]
 
@@ -349,6 +371,10 @@ Operating system version of the image.
 The time zone to use for the cloud VM cluster. For details, see Time
 Zones.
 
+--vault-id [text]
+
+The OCID of the Exadata Database Storage Vault.
+
 --vm-cluster-type [text]
 
 The vmcluster type for the VM cluster/Cloud VM cluster.

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

@@ -79,7 +79,44 @@ via the file:// syntax.
 
 --cpu-core-count [integer]
 
-The number of CPU cores to enable for the cloud VM cluster.
+For fixed shapes, this is the total number of OCPUs to enable across
+the VM cluster.
+
+   * Exadata.Base.48 - Specify a multiple of 2, from 0 to 48.  -
+     Exadata.Quarter1.84 - Specify a multiple of 2, from 22 to 84.  -
+     Exadata.Half1.168 - Specify a multiple of 4, from 44 to 168.  -
+     Exadata.Full1.336 - Specify a multiple of 8, from 88 to 336.  -
+     Exadata.Quarter2.92 - Specify a multiple of 2, from 0 to 92.  -
+     Exadata.Half2.184 - Specify a multiple of 4, from 0 to 184.  -
+     Exadata.Full2.368 - Specify a multiple of 8, from 0 to 368.  -
+     Exadata.Quarter3.100 - Specify a multiple of 2, from 0 to 100.  -
+     Exadata.Half3.200 - Specify a multiple of 4, from 0 to 200.  -
+     Exadata.Full3.400 - Specify a multiple of 8, from 0 to 400.
+
+The API specification for fixed shape values is
+https://docs.oracle.com/en-
+us/iaas/api/#/en/database/20160918/DbSystemShapeSummary
+
+   For flexible shapes X8M and X9M, this is the total number of OCPUs
+   to enable across the VM cluster. The number available for the VM
+   cluster will be based on the number of database servers selected
+   for provisioning the VM cluster on the Exadata Infrastructure.
+
+   * Exadata.X8M - Specify a multiple of 2, from 2 to 50 per X8M
+     database server.  - Exadata.X9M - Specify a multiple of 2, from 2
+     to 126 per X9M database server.
+
+For flexible shapes X11M and higher, this is the total number of ECPUs
+to enable across the VM cluster. The number available for the VM
+cluster will be based on the number of database servers selected for
+provisioning the VM cluster on the Exadata Infrastructure.
+
+   * Exadata.X11M - Specify a multiple of 8, from 8 to 760 per X11M
+     database server.
+
+The API specification for flexible shape values is
+https://docs.oracle.com/en-
+us/iaas/api/#/en/database/20160918/datatypes/FlexComponentSummary
 
 --data-collection-options [complex type]
 

oci_cli/help_text_producer/data_files/text/cmdref/db/exascale-db-storage-vault/create.txt

@@ -76,7 +76,7 @@ via the file:// syntax.
 
 Exadata Database Storage Vault description.
 
---exadata-infrastructure-id [text]
+--exa-infra-id [text]
 
 The OCID of the Exadata infrastructure.
 

oci_cli/help_text_producer/data_files/text/cmdref/db/exascale-db-storage-vault/list.txt

@@ -61,7 +61,7 @@ placement group ID exactly.
 A filter to return only resources that match the entire display name
 given. The match is not case sensitive.
 
---exadata-infrastructure-id [text]
+--exa-infra-id [text]
 
 A filter to return only list of Vaults that are linked to the exadata
 infrastructure Id.
@@ -88,6 +88,28 @@ 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
 
+--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
+
 --lifecycle-state [text]
 
 A filter to return only Exadata Database Storage Vaults that match the

oci_cli/help_text_producer/data_files/text/cmdref/db/system-shape.txt

@@ -9,6 +9,11 @@ The shape of the DB system. The shape determines resources to allocate
 to the DB system - CPU cores and memory for VM shapes; CPU cores,
 memory and storage for non-VM (or bare metal) shapes.
 
+For Exadata fixed and flexible shapes, detailed specifications can be
+found in https://docs.oracle.com/en/engineered-systems/exadata-cloud-
+service/ecscm/exa-service-desc.html#GUID-
+9E090174-5C57-4EB1-9243-B470F9F10D6B
+
 To use any of the API operations, you must be authorized in an IAM
 policy. If you’re not authorized, talk to an administrator. If you’re
 an administrator who needs to write policies to give users access, see

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

@@ -112,6 +112,8 @@ Available Commands
   * create-autonomous-database-create-cross-region-disaster-recovery-
     details
 
+  * create-autonomous-database-gcp-key-details
+
   * create-autonomous-database-undelete-autonomous-database-details
 
   * create-cross-tenancy-disaster-recovery-details
@@ -178,6 +180,8 @@ Available Commands
 
   * update
 
+  * update-autonomous-database-gcp-key-details
+
 * autonomous-database-backup
 
   * create
@@ -348,6 +352,8 @@ Available Commands
 
   * change-compartment
 
+  * configure-exascale
+
   * create
 
   * delete

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-collection/create-db.txt

@@ -31,7 +31,7 @@ Required Parameters
 
 --compartment-id, -c [text]
 
-Compartment Identifier
+The OCID of the Compartment.
 
 --service-type [text]
 
@@ -72,7 +72,7 @@ via the file:// syntax.
 
 --display-name [text]
 
-Exadata Fleet Update Collection Identifier.
+The user-friendly name for the Exadata Fleet Update Collection.
 
 --fleet-discovery [complex type]
 

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-collection/create-exadb-stack.txt

@@ -0,0 +1,173 @@
+"create-exadb-stack"
+********************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Creates a new Exadata Fleet Update Collection.
+
+
+Usage
+=====
+
+   oci fleet-software-update fsu-collection create-exadb-stack [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+The OCID of the Compartment.
+
+--components [complex type]
+
+Details of components in an Exadata software stack. 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.
+
+--service-type [text]
+
+Exadata service type for the target resource members.
+
+Accepted values are:
+
+   EXACC, EXACS
+
+
+Optional Parameters
+===================
+
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. 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.
+
+--display-name [text]
+
+The user-friendly name for the Exadata Fleet Update Collection.
+
+--freeform-tags [complex type]
+
+Simple key-value pair that is applied without any predefined name,
+type or scope. Exists for cross-compatibility only. 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
+
+--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, NEEDS_ATTENTION, 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 and paste the following example into a JSON file, replacing the
+example parameters with your own.
+
+       oci fleet-software-update fsu-collection create-exadb-stack --generate-param-json-input components > components.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 compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-software-update/fsu-collection/create-exadb-stack.html#cmdoption-compartment-id
+       export service_type=<substitute-value-of-service_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-software-update/fsu-collection/create-exadb-stack.html#cmdoption-service-type
+
+       oci fleet-software-update fsu-collection create-exadb-stack --compartment-id $compartment_id --components file://components.json --service-type $service_type

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-collection/create-gi.txt

@@ -31,7 +31,7 @@ Required Parameters
 
 --compartment-id, -c [text]
 
-Compartment Identifier
+The OCID of the Compartment.
 
 --service-type [text]
 
@@ -71,7 +71,7 @@ via the file:// syntax.
 
 --display-name [text]
 
-Exadata Fleet Update Collection Identifier.
+The user-friendly name for the Exadata Fleet Update Collection.
 
 --fleet-discovery [complex type]