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

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

@@ -64,7 +64,8 @@ Accepted values are:
 
 --db-workload [text]
 
-Possible workload types.
+Possible workload types. Currently only OLTP workload type is
+supported.
 
 Accepted values are:
 
@@ -77,7 +78,9 @@ The display name of the Globally distributed autonomous database.
 --listener-port [integer]
 
 The listener port number for the Globally distributed autonomous
-database.
+database. The listener port number has to be unique for a customer
+tenancy across all distributed autonomous databases. Same port number
+should not be re-used for any other distributed autonomous database.
 
 --ncharacter-set [text]
 
@@ -85,11 +88,17 @@ The national character set for the database.
 
 --ons-port-local [integer]
 
-Ons local port number.
+Ons local port number for Globally distributed autonomous database.
+The onsPortLocal has to be unique for a customer tenancy across all
+distributed autonomous databases. Same port number should not be re-
+used for any other distributed autonomous database.
 
 --ons-port-remote [integer]
 
-Ons remote port number.
+Ons remote port number for Globally distributed autonomous database.
+The onsPortRemote has to be unique for a customer tenancy across all
+distributed autonomous databases. Same port number should not be re-
+used for any other distributed autonomous database.
 
 --prefix [text]
 
@@ -136,9 +145,22 @@ Optional Parameters
 
 --chunks [integer]
 
-The default number of unique chunks in a shardspace. The value of
-chunks must be greater than 2 times the size of the largest shardgroup
-in any shardspace.
+Number of chunks in a shardspace. The value of chunks must be greater
+than 2 times the size of the largest shardgroup in any shardspace.
+Chunks is required to be provided for distributed autonomous databases
+being created with SYSTEM shardingMethod. For USER shardingMethod,
+chunks should not be set in create payload.
+
+--db-backup-config [complex type]
+
+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.
 
 --defined-tags [complex type]
 
@@ -191,7 +213,11 @@ nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
 --listener-port-tls [integer]
 
 The TLS listener port number for Globally distributed autonomous
-database.
+database. The TLS listener port number has to be unique for a customer
+tenancy across all distributed autonomous databases. Same port number
+should not be re-used for any other distributed autonomous database.
+The listenerPortTls is mandatory for dedicated infrastructure based
+distributed autonomous databases.
 
 --max-wait-seconds [integer]
 
@@ -206,8 +232,11 @@ autonomous database. Currently supported values are 3, 5 and 7.
 --replication-method [text]
 
 The Replication method for Globally distributed autonomous database.
-Use RAFT for Raft replication, and DG for DataGuard. If
-replicationMethod is not provided, it defaults to DG.
+Use RAFT for Raft based replication. With RAFT replication, shards
+cannot have peers details set on them. In case shards need to have
+peers, please do not set RAFT replicationMethod. For all non RAFT
+replication cases (with or without peers), please set
+replicationMethod as DG or do not set any value for replicationMethod.
 
 Accepted values are:
 
@@ -215,8 +244,9 @@ Accepted values are:
 
 --replication-unit [integer]
 
-For RAFT replication based Globally distributed autonomous database,
-the value should be atleast twice the number of shards.
+The replication unit count for RAFT based distributed autonomous
+database. For RAFT replication based Globally distributed autonomous
+database, the value should be at least twice the number of shards.
 
 --wait-for-state [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/distributed-database/distributed-autonomous-db-service/distributed-autonomous-database/rotate-distributed-autonomous-database-passwords.txt

@@ -17,8 +17,9 @@
 Description
 ===========
 
-Rotate passwords for different components of the Globally distributed
-autonomous database.
+Rotate the gsmuser and gsmcatuser passwords for shards and catalog of
+the Globally distributed autonomous database. This operation will also
+remove GdsCtlNodes if present.
 
 
 Usage

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

@@ -15,6 +15,8 @@ Available Commands
 
 * change-compartment
 
+* change-distributed-autonomous-db-backup-config
+
 * configure-distributed-autonomous-database-gsms
 
 * configure-distributed-autonomous-database-sharding

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

@@ -18,6 +18,8 @@ Available Commands
 
   * change-compartment
 
+  * change-distributed-autonomous-db-backup-config
+
   * configure-distributed-autonomous-database-gsms
 
   * configure-distributed-autonomous-database-sharding

oci_cli/help_text_producer/data_files/text/cmdref/distributed-database/distributed-db-service/distributed-database/create.txt

@@ -68,7 +68,10 @@ The display name of the Globally distributed database.
 
 --listener-port [integer]
 
-The listener port number for the Globally distributed database.
+The listener port number for the Globally distributed database. The
+listener port number has to be unique for a customer tenancy across
+all distributed databases. Same port number should not be re-used for
+any other distributed database.
 
 --ncharacter-set [text]
 
@@ -76,11 +79,17 @@ The national character set for the database.
 
 --ons-port-local [integer]
 
-Ons local port number.
+The ons local port number for the Globally distributed database. The
+onsPortLocal has to be unique for a customer tenancy across all
+distributed databases. Same port number should not be re-used for any
+other distributed database.
 
 --ons-port-remote [integer]
 
-Ons remote port number.
+The ons remote port number for the Globally distributed database. The
+onsPortRemote has to be unique for a customer tenancy across all
+distributed databases. Same port number should not be re-used for any
+other distributed database.
 
 --prefix [text]
 
@@ -127,9 +136,11 @@ Optional Parameters
 
 --chunks [integer]
 
-The default number of unique chunks in a shardspace. The value of
-chunks must be greater than 2 times the size of the largest shardgroup
-in any shardspace.
+Number of chunks in a shardspace. The value of chunks must be greater
+than 2 times the size of the largest shardgroup in any shardspace.
+Chunks is required to be provided for distributed databases being
+created with SYSTEM shardingMethod. For USER shardingMethod, chunks
+should not be set in create payload.
 
 --db-backup-config [complex type]
 
@@ -196,7 +207,12 @@ The SSH public key for Global service manager instances.
 
 --listener-port-tls [integer]
 
-The TLS listener port number for Globally distributed database.
+The TLS listener port number for the Globally distributed database.
+The TLS listener port number has to be unique for a customer tenancy
+across all distributed databases. Same port number should not be re-
+used for any other distributed database. For BASE_DB and EXADB_XS
+based distributed databases, tls is not supported hence the
+listenerPortTls is not needed to be provided in create payload.
 
 --max-wait-seconds [integer]
 
@@ -211,8 +227,11 @@ database. Currently supported values are 3, 5 and 7.
 --replication-method [text]
 
 The Replication method for Globally distributed database. Use RAFT for
-Raft replication, and DG for DataGuard. If replicationMethod is not
-provided, it defaults to DG.
+Raft based replication. With RAFT replication, shards cannot have
+peers details set on them. In case shards need to have peers, please
+do not set RAFT replicationMethod. For all non RAFT replication cases
+(with or without peers), please set replicationMethod as DG or do not
+set any value for replicationMethod.
 
 Accepted values are:
 
@@ -220,8 +239,9 @@ Accepted values are:
 
 --replication-unit [integer]
 
-For RAFT replication based Globally distributed database, the value
-should be atleast twice the number of shards.
+The replication unit count for RAFT based distributed database. For
+RAFT replication based Globally distributed database, the value should
+be at least twice the number of shards.
 
 --wait-for-state [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/distributed-database/distributed-db-service/distributed-database/rotate-distributed-database-passwords.txt

@@ -17,8 +17,9 @@
 Description
 ===========
 
-Rotate passwords for different components of the Globally distributed
-database.
+Rotate the gsmuser and gsmcatuser passwords for shards and catalog of
+the Globally distributed database.  This operation will also remove
+GdsCtlNodes if present.
 
 
 Usage

oci_cli/help_text_producer/data_files/text/cmdref/distributed-database.txt

@@ -20,6 +20,8 @@ Available Commands
 
     * change-compartment
 
+    * change-distributed-autonomous-db-backup-config
+
     * configure-distributed-autonomous-database-gsms
 
     * configure-distributed-autonomous-database-sharding

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/compliance/get.txt

@@ -0,0 +1,99 @@
+"get"
+*****
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Retrieve compliance for a fleet.
+
+
+Usage
+=====
+
+   oci fleet-apps-management compliance get [OPTIONS]
+
+
+Required Parameters
+===================
+
+--fleet-id [text]
+
+Unique Fleet identifier.
+
+
+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
+
+
+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-apps-management fleet create --generate-param-json-input resource-selection > resource-selection.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-apps-management/fleet/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/fleet-apps-management/fleet/create.html#cmdoption-display-name
+
+       fleet_id=$(oci fleet-apps-management fleet create --compartment-id $compartment_id --display-name $display_name --resource-selection file://resource-selection.json --query data.id --raw-output)
+
+       oci fleet-apps-management compliance get --fleet-id $fleet_id

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/compliance.txt

@@ -0,0 +1,14 @@
+compliance
+**********
+
+
+Description
+===========
+
+Compliance Summary
+
+
+Available Commands
+==================
+
+* get

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet/create-fleet-dynamic-resource-selection.txt

@@ -178,10 +178,11 @@ The OCID of the fleet that would be the parent for this fleet.
 
 --products [complex type]
 
-Products associated with the Fleet. 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.
+Products associated with the Fleet. Provide PlatformConfiguration Ids
+corresponding to all the Products that need to be managed. 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

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet/create-fleet-environment-fleet-details.txt

@@ -167,10 +167,11 @@ The OCID of the fleet that would be the parent for this fleet.
 
 --products [complex type]
 
-Products associated with the Fleet. 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.
+Products associated with the Fleet. Provide PlatformConfiguration Ids
+corresponding to all the Products that need to be managed. 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

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet/create-fleet-generic-fleet-details.txt

@@ -167,10 +167,11 @@ The OCID of the fleet that would be the parent for this fleet.
 
 --products [complex type]
 
-Products associated with the Fleet. 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.
+Products associated with the Fleet. Provide PlatformConfiguration Ids
+corresponding to all the Products that need to be managed. 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

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet/create-fleet-group-fleet-details.txt

@@ -167,10 +167,11 @@ The OCID of the fleet that would be the parent for this fleet.
 
 --products [complex type]
 
-Products associated with the Fleet. 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.
+Products associated with the Fleet. Provide PlatformConfiguration Ids
+corresponding to all the Products that need to be managed. 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

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet/create-fleet-manual-resource-selection.txt

@@ -167,10 +167,11 @@ The OCID of the fleet that would be the parent for this fleet.
 
 --products [complex type]
 
-Products associated with the Fleet. 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.
+Products associated with the Fleet. Provide PlatformConfiguration Ids
+corresponding to all the Products that need to be managed. 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

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet/create-fleet-product-fleet-details.txt

@@ -167,10 +167,11 @@ The OCID of the fleet that would be the parent for this fleet.
 
 --products [complex type]
 
-Products associated with the Fleet. 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.
+Products associated with the Fleet. Provide PlatformConfiguration Ids
+corresponding to all the Products that need to be managed. 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

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet/create.txt

@@ -178,10 +178,11 @@ The OCID of the fleet that would be the parent for this fleet.
 
 --products [complex type]
 
-Products associated with the Fleet. 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.
+Products associated with the Fleet. Provide PlatformConfiguration Ids
+corresponding to all the Products that need to be managed. 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

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet/update-fleet-dynamic-resource-selection.txt

@@ -75,6 +75,11 @@ Example:
 
    My new resource
 
+--environment-type [text]
+
+Environment Type associated with the Fleet. Applicable for ENVIRONMENT
+fleet types.
+
 --force
 
 Perform update without prompting for confirmation.
@@ -153,10 +158,11 @@ via the file:// syntax.
 
 --products [complex type]
 
-Products associated with the Fleet. 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.
+Products associated with the Fleet. Provide PlatformConfiguration Ids
+corresponding to all the Products that need to be managed. 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

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet/update-fleet-manual-resource-selection.txt

@@ -64,6 +64,11 @@ Example:
 
    My new resource
 
+--environment-type [text]
+
+Environment Type associated with the Fleet. Applicable for ENVIRONMENT
+fleet types.
+
 --force
 
 Perform update without prompting for confirmation.
@@ -142,10 +147,11 @@ via the file:// syntax.
 
 --products [complex type]
 
-Products associated with the Fleet. 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.
+Products associated with the Fleet. Provide PlatformConfiguration Ids
+corresponding to all the Products that need to be managed. 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

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet/update.txt

@@ -64,6 +64,11 @@ Example:
 
    My new resource
 
+--environment-type [text]
+
+Environment Type associated with the Fleet. Applicable for ENVIRONMENT
+fleet types.
+
 --force
 
 Perform update without prompting for confirmation.
@@ -142,10 +147,11 @@ via the file:// syntax.
 
 --products [complex type]
 
-Products associated with the Fleet. 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.
+Products associated with the Fleet. Provide PlatformConfiguration Ids
+corresponding to all the Products that need to be managed. 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

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-admin/onboarding/create.txt

@@ -39,6 +39,32 @@ Tenancy OCID
 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.
+
+--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

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-admin/onboarding/update.txt

@@ -38,6 +38,36 @@ given identifier.
 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.
+
+--force
+
+Perform update without prompting for confirmation.
+
+--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