oci-cli 3.71.4__py3-none-any.whl → 3.72.0__py3-none-any.whl

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

@@ -69,6 +69,17 @@ control list (ACL) for standby compared to primary.
 The Autonomous Container Database OCID. Used only by Autonomous AI
 Database on Dedicated Exadata Infrastructure.
 
+--autonomous-database-maintenance-window [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.
+
 --autonomous-maintenance-schedule-type [text]
 
 The maintenance schedule type of the Autonomous AI Database

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-cross-tenancy-disaster-recovery-details.txt

@@ -78,6 +78,17 @@ control list (ACL) for standby compared to primary.
 The Autonomous Container Database OCID. Used only by Autonomous AI
 Database on Dedicated Exadata Infrastructure.
 
+--autonomous-database-maintenance-window [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.
+
 --autonomous-maintenance-schedule-type [text]
 
 The maintenance schedule type of the Autonomous AI Database

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-from-backup-id.txt

@@ -85,6 +85,17 @@ control list (ACL) for standby compared to primary.
 The Autonomous Container Database OCID. Used only by Autonomous AI
 Database on Dedicated Exadata Infrastructure.
 
+--autonomous-database-maintenance-window [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.
+
 --backup-retention-period-in-days [integer]
 
 Retention period, in days, for long-term backups

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-from-backup-timestamp.txt

@@ -85,6 +85,17 @@ control list (ACL) for standby compared to primary.
 The Autonomous Container Database OCID. Used only by Autonomous AI
 Database on Dedicated Exadata Infrastructure.
 
+--autonomous-database-maintenance-window [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.
+
 --backup-retention-period-in-days [integer]
 
 Retention period, in days, for long-term backups

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

@@ -87,6 +87,17 @@ control list (ACL) for standby compared to primary.
 The Autonomous Container Database OCID. Used only by Autonomous AI
 Database on Dedicated Exadata Infrastructure.
 
+--autonomous-database-maintenance-window [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.
+
 --backup-retention-period-in-days [integer]
 
 Retention period, in days, for long-term backups

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

@@ -92,6 +92,17 @@ refresh happens.
 The Autonomous Container Database OCID. Used only by Autonomous AI
 Database on Dedicated Exadata Infrastructure.
 
+--autonomous-database-maintenance-window [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.
+
 --backup-retention-period-in-days [integer]
 
 Retention period, in days, for long-term backups

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

@@ -74,6 +74,17 @@ control list (ACL) for standby compared to primary.
 The Autonomous Container Database OCID. Used only by Autonomous AI
 Database on Dedicated Exadata Infrastructure.
 
+--autonomous-database-maintenance-window [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.
+
 --backup-retention-period-in-days [integer]
 
 Retention period, in days, for long-term backups

oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/update-autonomous-database-gcp-key-details.txt

@@ -97,6 +97,17 @@ mins means refresh to the latest available timestamp). The maximum is
 7 days. The lag time increases after refreshing until the next data
 refresh happens.
 
+--autonomous-database-maintenance-window [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.
+
 --autonomous-maintenance-schedule-type [text]
 
 The maintenance schedule type of the Autonomous AI Database
@@ -562,6 +573,16 @@ Parameter that allows users to select an acceptable maximum data loss
 limit in seconds, up to which Automatic Failover will be triggered
 when necessary for a Local Autonomous Data Guard
 
+--local-adg-resource-pool-leader-id [text]
+
+The OCID of a dedicated resource pool leader Autonomous AI Database in
+the same region, that is required when local Autonomous Data Guard is
+enabled for a dedicated resource pool member using the parameter
+*isLocalDataGuardEnabled*. This field applies only to dedicated
+resource pool members, and the specified leader must be different from
+the primary’s leader. Local Autonomous Data Guard can be enabled only
+if more than one dedicated resource pool exists in the region.
+
 --long-term-backup-schedule [complex type]
 
 This is a complex type whose value must be valid JSON. The value can
@@ -808,6 +829,93 @@ on the database instance. Specifying an overlapping subnet will cause
 the private interconnect to malfunction. This restriction applies to
 both the client subnet and the backup subnet.
 
+--time-maintenance-pause-until [datetime]
+
+The date until which maintenance of Autonomous AI Database is
+temporarily paused.
+
+   The following datetime formats are supported:
+
+
+UTC with microseconds
+---------------------
+
+   Format: YYYY-MM-DDTHH:mm:ss.ssssssTZD
+   Example: 2017-09-15T20:30:00.123456Z
+
+   UTC with milliseconds
+   ***********************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ss.sssTZD
+       Example: 2017-09-15T20:30:00.123Z
+
+   UTC without milliseconds
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T20:30:00Z
+
+   UTC with minute precision
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T20:30Z
+
+
+Timezone with microseconds
+--------------------------
+
+   Format: YYYY-MM-DDTHH:mm:ssTZD
+   Example: 2017-09-15T12:30:00.456789-08:00, 2017-09-15T12:30:00.456789-0800
+
+   Timezone with milliseconds
+   ***************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00.456-08:00, 2017-09-15T12:30:00.456-0800
+
+   Timezone without milliseconds
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00-08:00, 2017-09-15T12:30:00-0800
+
+   Timezone with minute precision
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T12:30-08:00, 2017-09-15T12:30-0800
+
+   Short date and time
+   ********************
+   The timezone for this date and time will be taken as UTC (Needs to be surrounded by single or double quotes)
+
+   .. code::
+
+       Format: 'YYYY-MM-DD HH:mm' or "YYYY-MM-DD HH:mm"
+       Example: '2017-09-15 17:25'
+
+   Date Only
+   **********
+   This date will be taken as midnight UTC of that day
+
+   .. code::
+
+       Format: YYYY-MM-DD
+       Example: 2017-09-15
+
+   Epoch seconds
+   **************
+   .. code::
+
+       Example: 1412195400
+
 --time-of-auto-refresh-start [datetime]
 
 The the date and time that auto-refreshing will begin for an

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

@@ -81,6 +81,17 @@ mins means refresh to the latest available timestamp). The maximum is
 7 days. The lag time increases after refreshing until the next data
 refresh happens.
 
+--autonomous-database-maintenance-window [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.
+
 --autonomous-maintenance-schedule-type [text]
 
 The maintenance schedule type of the Autonomous AI Database
@@ -552,6 +563,16 @@ Parameter that allows users to select an acceptable maximum data loss
 limit in seconds, up to which Automatic Failover will be triggered
 when necessary for a Local Autonomous Data Guard
 
+--local-adg-resource-pool-leader-id [text]
+
+The OCID of a dedicated resource pool leader Autonomous AI Database in
+the same region, that is required when local Autonomous Data Guard is
+enabled for a dedicated resource pool member using the parameter
+*isLocalDataGuardEnabled*. This field applies only to dedicated
+resource pool members, and the specified leader must be different from
+the primary’s leader. Local Autonomous Data Guard can be enabled only
+if more than one dedicated resource pool exists in the region.
+
 --long-term-backup-schedule [complex type]
 
 This is a complex type whose value must be valid JSON. The value can
@@ -798,6 +819,93 @@ on the database instance. Specifying an overlapping subnet will cause
 the private interconnect to malfunction. This restriction applies to
 both the client subnet and the backup subnet.
 
+--time-maintenance-pause-until [datetime]
+
+The date until which maintenance of Autonomous AI Database is
+temporarily paused.
+
+   The following datetime formats are supported:
+
+
+UTC with microseconds
+---------------------
+
+   Format: YYYY-MM-DDTHH:mm:ss.ssssssTZD
+   Example: 2017-09-15T20:30:00.123456Z
+
+   UTC with milliseconds
+   ***********************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ss.sssTZD
+       Example: 2017-09-15T20:30:00.123Z
+
+   UTC without milliseconds
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T20:30:00Z
+
+   UTC with minute precision
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T20:30Z
+
+
+Timezone with microseconds
+--------------------------
+
+   Format: YYYY-MM-DDTHH:mm:ssTZD
+   Example: 2017-09-15T12:30:00.456789-08:00, 2017-09-15T12:30:00.456789-0800
+
+   Timezone with milliseconds
+   ***************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00.456-08:00, 2017-09-15T12:30:00.456-0800
+
+   Timezone without milliseconds
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00-08:00, 2017-09-15T12:30:00-0800
+
+   Timezone with minute precision
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T12:30-08:00, 2017-09-15T12:30-0800
+
+   Short date and time
+   ********************
+   The timezone for this date and time will be taken as UTC (Needs to be surrounded by single or double quotes)
+
+   .. code::
+
+       Format: 'YYYY-MM-DD HH:mm' or "YYYY-MM-DD HH:mm"
+       Example: '2017-09-15 17:25'
+
+   Date Only
+   **********
+   This date will be taken as midnight UTC of that day
+
+   .. code::
+
+       Format: YYYY-MM-DD
+       Example: 2017-09-15
+
+   Epoch seconds
+   **************
+   .. code::
+
+       Example: 1412195400
+
 --time-of-auto-refresh-start [datetime]
 
 The the date and time that auto-refreshing will begin for an

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

@@ -0,0 +1,174 @@
+"create-database-create-database-from-database"
+***********************************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Creates a new database in the specified Database Home. If the database
+version is provided, it must match the version of the Database Home.
+Applies to Exadata and Exadata Cloud@Customer systems.
+
+
+Usage
+=====
+
+   oci db database create-database-create-database-from-database [OPTIONS]
+
+
+Required Parameters
+===================
+
+--database [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.
+
+--db-home-id [text]
+
+The OCID of the Database Home.
+
+
+Optional Parameters
+===================
+
+--db-version [text]
+
+A valid Oracle Database version. For a list of supported versions, use
+the ListDbVersions operation.
+
+This cannot be updated in parallel with any of the following:
+licenseModel, dbEdition, cpuCoreCount, computeCount, computeModel,
+adminPassword, whitelistedIps, isMTLSConnectionRequired, openMode,
+permissionLevel, dbWorkload, privateEndpointLabel, nsgIds,
+isRefreshable, dbName, scheduledOperations, dbToolsDetails,
+isLocalDataGuardEnabled, or isFreeTier.
+
+--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
+
+--kms-key-id [text]
+
+The OCID of the key container that is used as the master encryption
+key in database transparent data encryption (TDE) operations.
+
+--kms-key-version-id [text]
+
+The OCID of the key container version that is used in database
+transparent data encryption (TDE) operations KMS Key can have multiple
+key versions. If none is specified, the current key version (latest)
+of the Key Id is used for the operation. Autonomous AI Database
+Serverless does not use key versions, hence is not applicable for
+Autonomous AI Database Serverless instances.
+
+--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.
+
+--opc-dry-run [boolean]
+
+Indicates that the request is a dry run, if set to “true”. A dry run
+request does not actually creating or updating a resource and is used
+only to perform validation on the submitted data.
+
+--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, BACKUP_IN_PROGRESS, CONVERTING, FAILED, PROVISIONING, RESTORE_FAILED, TERMINATED, TERMINATING, UPDATING, UPGRADING
+
+--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", "--enable-dual-stack", "--enable-propagation", "--
+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 database create-database-create-database-from-database --generate-param-json-input database > database.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 db_system_id=<substitute-value-of-db_system_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/db-home/create.html#cmdoption-db-system-id
+       export admin_password=<substitute-value-of-admin_password> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/database/create.html#cmdoption-admin-password
+       export db_name=<substitute-value-of-db_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/database/create.html#cmdoption-db-name
+
+       db_home_id=$(oci db db-home create --db-system-id $db_system_id --query data.id --raw-output)
+
+       database_id=$(oci db database create --admin-password $admin_password --db-home-id $db_home_id --db-name $db_name --db-system-id $db_system_id --query data.id --raw-output)
+
+       oci db database create-database-create-database-from-database --database file://database.json --db-home-id $db_home_id

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

@@ -269,7 +269,7 @@ for creating a new database by restoring from a database backup.
 
 Accepted values are:
 
-   DATABASE, DB_BACKUP, NONE, VM_CLUSTER_BACKUP, VM_CLUSTER_NEW
+   DATABASE, DB_BACKUP, NONE, VM_CLUSTER_BACKUP, VM_CLUSTER_DATABASE, VM_CLUSTER_NEW
 
 --tde-wallet-password [text]
 

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

@@ -43,6 +43,8 @@ Available Commands
 
 * create
 
+* create-database-create-database-from-database
+
 * create-database-create-stand-by-database-details
 
 * create-database-from-backup