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/create-autonomous-database-gcp-key-details.txt

@@ -0,0 +1,779 @@
+"create-autonomous-database-gcp-key-details"
+********************************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Creates a new Autonomous Database.
+
+
+Usage
+=====
+
+   oci db autonomous-database create-autonomous-database-gcp-key-details [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+The OCID of the compartment of the Autonomous Database.
+
+--encryption-key-key-name [text]
+
+GCP key name
+
+--encryption-key-key-ring [text]
+
+GCP key ring
+
+--encryption-key-location [text]
+
+GCP key ring location
+
+--encryption-key-project [text]
+
+GCP project name
+
+
+Optional Parameters
+===================
+
+--admin-password [text]
+
+**Important** The *adminPassword* or *secretId* must be specified for
+all Autonomous Databases except for refreshable clones. The password
+must be between 12 and 30 characters long, and must contain at least 1
+uppercase, 1 lowercase, and 1 numeric character. It cannot contain the
+double quote symbol (“) or the username “admin”, regardless of casing.
+
+This cannot be used in conjunction with with OCI vault secrets
+(secretId).
+
+--are-primary-whitelisted-ips-used [boolean]
+
+This field will be null if the Autonomous Database is not Data Guard
+enabled or Access Control is disabled. It’s value would be *TRUE* if
+Autonomous Database is Data Guard enabled and Access Control is
+enabled and if the Autonomous Database uses primary IP access control
+list (ACL) for standby. It’s value would be *FALSE* if Autonomous
+Database is Data Guard enabled and Access Control is enabled and if
+the Autonomous Database uses different IP access control list (ACL)
+for standby compared to primary.
+
+--autonomous-container-database-id [text]
+
+The Autonomous Container Database OCID. Used only by Autonomous
+Database on Dedicated Exadata Infrastructure.
+
+--autonomous-maintenance-schedule-type [text]
+
+The maintenance schedule type of the Autonomous Database Serverless.
+An EARLY maintenance schedule follows a schedule applying patches
+prior to the REGULAR schedule. A REGULAR maintenance schedule follows
+the normal cycle
+
+Accepted values are:
+
+   EARLY, REGULAR
+
+--backup-retention-period-in-days [integer]
+
+Retention period, in days, for long-term backups
+
+--byol-compute-count-limit [float]
+
+The maximum number of CPUs allowed with a Bring Your Own License
+(BYOL), including those used for auto-scaling, disaster recovery,
+tools, etc. Any CPU usage above this limit is considered as License
+Included and billed.
+
+--character-set [text]
+
+The character set for the autonomous database. The default is
+AL32UTF8. Allowed values for an Autonomous Database Serverless
+instance as as returned by List Autonomous Database Character Sets
+
+For an Autonomous Database on dedicated infrastructure, the allowed
+values are:
+
+AL32UTF8, AR8ADOS710, AR8ADOS720, AR8APTEC715, AR8ARABICMACS,
+AR8ASMO8X, AR8ISO8859P6, AR8MSWIN1256, AR8MUSSAD768, AR8NAFITHA711,
+AR8NAFITHA721, AR8SAKHR706, AR8SAKHR707, AZ8ISO8859P9E, BG8MSWIN,
+BG8PC437S, BLT8CP921, BLT8ISO8859P13, BLT8MSWIN1257, BLT8PC775,
+BN8BSCII, CDN8PC863, CEL8ISO8859P14, CL8ISO8859P5, CL8ISOIR111,
+CL8KOI8R, CL8KOI8U, CL8MACCYRILLICS, CL8MSWIN1251, EE8ISO8859P2,
+EE8MACCES, EE8MACCROATIANS, EE8MSWIN1250, EE8PC852, EL8DEC,
+EL8ISO8859P7, EL8MACGREEKS, EL8MSWIN1253, EL8PC437S, EL8PC851,
+EL8PC869, ET8MSWIN923, HU8ABMOD, HU8CWI2, IN8ISCII, IS8PC861,
+IW8ISO8859P8, IW8MACHEBREWS, IW8MSWIN1255, IW8PC1507, JA16EUC,
+JA16EUCTILDE, JA16SJIS, JA16SJISTILDE, JA16VMS, KO16KSC5601,
+KO16KSCCS, KO16MSWIN949, LA8ISO6937, LA8PASSPORT, LT8MSWIN921,
+LT8PC772, LT8PC774, LV8PC1117, LV8PC8LR, LV8RST104090, N8PC865,
+NE8ISO8859P10, NEE8ISO8859P4, RU8BESTA, RU8PC855, RU8PC866,
+SE8ISO8859P3, TH8MACTHAIS, TH8TISASCII, TR8DEC, TR8MACTURKISHS,
+TR8MSWIN1254, TR8PC857, US7ASCII, US8PC437, UTF8, VN8MSWIN1258,
+VN8VN3, WE8DEC, WE8DG, WE8ISO8859P1, WE8ISO8859P15, WE8ISO8859P9,
+WE8MACROMAN8S, WE8MSWIN1252, WE8NCR4970, WE8NEXTSTEP, WE8PC850,
+WE8PC858, WE8PC860, WE8ROMAN8, ZHS16CGB231280, ZHS16GBK, ZHT16BIG5,
+ZHT16CCDC, ZHT16DBT, ZHT16HKSCS, ZHT16MSWIN950, ZHT32EUC, ZHT32SOPS,
+ZHT32TRIS
+
+--compute-count [float]
+
+The compute amount (CPUs) available to the database. Minimum and
+maximum values depend on the compute model and whether the database is
+an Autonomous Database Serverless instance or an Autonomous Database
+on Dedicated Exadata Infrastructure. The ‘ECPU’ compute model requires
+a minimum value of one, for databases in the elastic resource pool and
+minimum value of two, otherwise. Required when using the
+*computeModel* parameter. When using *cpuCoreCount* parameter, it is
+an error to specify computeCount to a non-null value. Providing
+*computeModel* and *computeCount* is the preferred method for both
+OCPU and ECPU.
+
+--compute-model [text]
+
+The compute model of the Autonomous Database. This is required if
+using the *computeCount* parameter. If using *cpuCoreCount* then it is
+an error to specify *computeModel* to a non-null value. ECPU compute
+model is the recommended model and OCPU compute model is legacy.
+
+Accepted values are:
+
+   ECPU, OCPU
+
+--cpu-core-count [integer]
+
+The number of CPU cores to be made available to the database. For
+Autonomous Databases on dedicated Exadata infrastructure, the maximum
+number of cores is determined by the infrastructure shape. See
+Characteristics of Infrastructure Shapes for shape details.
+
+**Note:** This parameter cannot be used with the *ocpuCount*
+parameter.
+
+--customer-contacts [complex type]
+
+Customer Contacts.
+
+This option is a JSON list with items of type CustomerContact.  For
+documentation on CustomerContact please see our API reference: https:
+//docs.cloud.oracle.com/api/#/en/database/20160918/datatypes/Customer
+Contact. 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.
+
+--data-storage-size-in-gbs [integer]
+
+The size, in gigabytes, of the data volume that will be created and
+attached to the database. This storage can later be scaled up if
+needed. The maximum storage value is determined by the infrastructure
+shape. See Characteristics of Infrastructure Shapes for shape details.
+
+**Notes** - This parameter is only supported for dedicated Exadata
+infrastructure. - This parameter cannot be used with the
+*dataStorageSizeInTBs* parameter.
+
+--data-storage-size-in-tbs [integer]
+
+The size, in terabytes, of the data volume that will be created and
+attached to the database. This storage can later be scaled up if
+needed. For Autonomous Databases on dedicated Exadata infrastructure,
+the maximum storage value is determined by the infrastructure shape.
+See Characteristics of Infrastructure Shapes for shape details. A full
+Exadata service is allocated when the Autonomous Database size is set
+to the upper limit (384 TB).
+
+**Note:** This parameter cannot be used with the
+*dataStorageSizeInGBs* parameter.
+
+--database-edition [text]
+
+The Oracle Database Edition that applies to the Autonomous databases.
+This parameter accepts options *STANDARD_EDITION* and
+*ENTERPRISE_EDITION*.
+
+--db-name [text]
+
+The database name. The name must begin with an alphabetic character
+and can contain a maximum of 30 alphanumeric characters. Special
+characters are not permitted. The database name must be unique in the
+tenancy. It is required in all cases except when creating a cross-
+region Autonomous Data Guard standby instance or a cross-region
+disaster recovery standby instance.
+
+--db-tools-details [complex type]
+
+The list of database tools details.
+
+This cannot be updated in parallel with any of the following:
+licenseModel, dbEdition, cpuCoreCount, computeCount, computeModel,
+whitelistedIps, isMTLSConnectionRequired, openMode, permissionLevel,
+dbWorkload, privateEndpointLabel, nsgIds, dbVersion, isRefreshable,
+dbName, scheduledOperations, isLocalDataGuardEnabled, or isFreeTier.
+
+This option is a JSON list with items of type DatabaseTool.  For
+documentation on DatabaseTool please see our API reference: https://d
+ocs.cloud.oracle.com/api/#/en/database/20160918/datatypes/DatabaseToo
+l. 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-version [text]
+
+A valid Oracle Database version for Autonomous Database.
+
+--db-workload [text]
+
+The Autonomous Database workload type. The following values are valid:
+
+* OLTP - indicates an Autonomous Transaction Processing database - DW
+  - indicates an Autonomous Data Warehouse database - AJD - indicates
+  an Autonomous JSON Database - APEX - indicates an Autonomous
+  Database with the Oracle APEX Application Development workload type.
+
+This cannot be updated in parallel with any of the following:
+licenseModel, dbEdition, cpuCoreCount, computeCount, computeModel,
+adminPassword, whitelistedIps, isMTLSConnectionRequired,
+privateEndpointLabel, nsgIds, dbVersion, isRefreshable, dbName,
+scheduledOperations, dbToolsDetails, isLocalDataGuardEnabled, or
+isFreeTier.
+
+Accepted values are:
+
+   AJD, APEX, DW, OLTP
+
+--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.
+
+--display-name [text]
+
+The user-friendly name for the Autonomous Database. The name does not
+have to be unique.
+
+--encryption-key-kms-rest-endpoint [text]
+
+GCP kms REST API endpoint
+
+--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
+
+--in-memory-percentage [integer]
+
+The percentage of the System Global Area(SGA) assigned to In-Memory
+tables in Autonomous Database. This property is applicable only to
+Autonomous Databases on the Exadata Cloud@Customer platform.
+
+--is-access-control-enabled [boolean]
+
+Indicates if the database-level access control is enabled. If
+disabled, database access is defined by the network security rules. If
+enabled, database access is restricted to the IP addresses defined by
+the rules specified with the *whitelistedIps* property. While
+specifying *whitelistedIps* rules is optional,  if database-level
+access control is enabled and no rules are specified, the database
+will become inaccessible. The rules can be added later using the
+*UpdateAutonomousDatabase* API operation or edit option in console.
+When creating a database clone, the desired access control setting
+should be specified. By default, database-level access control will be
+disabled for the clone.
+
+This property is applicable only to Autonomous Databases on the
+Exadata Cloud@Customer platform. For Autonomous Database Serverless
+instances, *whitelistedIps* is used.
+
+--is-auto-scaling-enabled [boolean]
+
+Indicates if auto scaling is enabled for the Autonomous Database CPU
+core count. The default value is *TRUE*.
+
+--is-auto-scaling-for-storage-enabled [boolean]
+
+Indicates if auto scaling is enabled for the Autonomous Database
+storage. The default value is *FALSE*.
+
+--is-backup-retention-locked [boolean]
+
+True if the Autonomous Database is backup retention locked.
+
+--is-data-guard-enabled [boolean]
+
+**Deprecated.** Indicates whether the Autonomous Database has local
+(in-region) Data Guard enabled. Not applicable to cross-region
+Autonomous Data Guard associations, or to Autonomous Databases using
+dedicated Exadata infrastructure or Exadata Cloud@Customer
+infrastructure.
+
+--is-dedicated [boolean]
+
+True if the database is on dedicated Exadata infrastructure.
+
+--is-dev-tier [boolean]
+
+Autonomous Database for Developers are fixed-shape Autonomous
+Databases that developers can use to build and test new applications.
+On Serverless, these are low-cost and billed per instance, on
+Dedicated and Cloud@Customer there is no additional cost to create
+Developer databases. Developer databases come with limited resources
+and is not intended for large-scale testing and production
+deployments. When you need more compute or storage resources, you may
+upgrade to a full paid production database.
+
+--is-free-tier [boolean]
+
+Indicates if this is an Always Free resource. The default value is
+false. Note that Always Free Autonomous Databases have 1 CPU and 20GB
+of memory. For Always Free databases, memory and CPU cannot be scaled.
+
+This cannot be updated in parallel with any of the following:
+licenseModel, dbEdition, cpuCoreCount, computeCount, computeModel,
+adminPassword, whitelistedIps, isMTLSConnectionRequired, openMode,
+permissionLevel, privateEndpointLabel, nsgIds, dbVersion,
+isRefreshable, dbName, scheduledOperations, dbToolsDetails, or
+isLocalDataGuardEnabled
+
+--is-local-data-guard-enabled [boolean]
+
+Indicates whether the Autonomous Database has local (in-region) Data
+Guard enabled. Not applicable to cross-region Autonomous Data Guard
+associations, or to Autonomous Databases using dedicated Exadata
+infrastructure or Exadata Cloud@Customer infrastructure.
+
+--is-mtls-connection-required [boolean]
+
+Specifies if the Autonomous Database requires mTLS connections.
+
+This may not be updated in parallel with any of the following:
+licenseModel, databaseEdition, cpuCoreCount, computeCount,
+dataStorageSizeInTBs, whitelistedIps, openMode, permissionLevel, db-
+workload, privateEndpointLabel, nsgIds, customerContacts, dbVersion,
+scheduledOperations, dbToolsDetails, isLocalDataGuardEnabled, or
+isFreeTier.
+
+Service Change: The default value of the isMTLSConnectionRequired
+attribute will change from true to false on July 1, 2023 in the
+following APIs: - CreateAutonomousDatabase - GetAutonomousDatabase -
+UpdateAutonomousDatabase Details: Prior to the July 1, 2023 change,
+the isMTLSConnectionRequired attribute default value was true. This
+applies to Autonomous Database Serverless. Does this impact me? If you
+use or maintain custom scripts or Terraform scripts referencing the
+CreateAutonomousDatabase, GetAutonomousDatabase, or
+UpdateAutonomousDatabase APIs, you want to check, and possibly modify,
+the scripts for the changed default value of the attribute. Should you
+choose not to leave your scripts unchanged, the API calls containing
+this attribute will continue to work, but the default value will
+switch from true to false. How do I make this change? Using either OCI
+SDKs or command line tools, update your custom scripts to explicitly
+set the isMTLSConnectionRequired attribute to true.
+
+--is-preview-version-with-service-terms-accepted [boolean]
+
+If set to *TRUE*, indicates that an Autonomous Database preview
+version is being provisioned, and that the preview version’s terms of
+service have been accepted. Note that preview version software is only
+available for Autonomous Database Serverless instances
+(https://docs.oracle.com/en/cloud/paas/autonomous-
+database/serverless/).
+
+--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.
+
+--license-model [text]
+
+The Oracle license model that applies to the Oracle Autonomous
+Database. Bring your own license (BYOL) allows you to apply your
+current on-premises Oracle software licenses to equivalent, highly
+automated Oracle services in the cloud. License Included allows you to
+subscribe to new Oracle Database software licenses and the Oracle
+Database service. Note that when provisioning an Autonomous Database
+on dedicated Exadata infrastructure, this attribute must be null. It
+is already set at the Autonomous Exadata Infrastructure level. When
+provisioning an Autonomous Database Serverless  database, if a value
+is not specified, the system defaults the value to
+*BRING_YOUR_OWN_LICENSE*. Bring your own license (BYOL) also allows
+you to select the DB edition using the optional parameter.
+
+This cannot be updated in parallel with any of the following:
+cpuCoreCount, computeCount, dataStorageSizeInTBs, adminPassword,
+isMTLSConnectionRequired, dbWorkload, privateEndpointLabel, nsgIds,
+dbVersion, dbName, scheduledOperations, dbToolsDetails, or isFreeTier.
+
+Accepted values are:
+
+   BRING_YOUR_OWN_LICENSE, LICENSE_INCLUDED
+
+--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.
+
+--ncharacter-set [text]
+
+The character set for the Autonomous Database. The default is
+AL32UTF8. Use List Autonomous Database Character Sets to list the
+allowed values for an Autonomous Database Serverless instance. For an
+Autonomous Database on dedicated Exadata infrastructure, the allowed
+values are: AL16UTF16 or UTF8.
+
+--nsg-ids [complex type]
+
+The list of OCIDs for the network security groups (NSGs) to which this
+resource belongs. Setting this to an empty list removes all resources
+from all NSGs. For more information about NSGs, see Security Rules.
+**NsgIds restrictions:** - A network security group (NSG) is optional
+for Autonomous Databases with private access. The nsgIds list can be
+empty. 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.
+
+--ocpu-count [float]
+
+The number of OCPU cores to be made available to the database.
+
+The following points apply: - For Autonomous Databases on Dedicated
+Exadata infrastructure, to provision less than 1 core, enter a
+fractional value in an increment of 0.1. For example, you can
+provision 0.3 or 0.4 cores, but not 0.35 cores. (Note that fractional
+OCPU values are not supported for Autonomous Database Serverless
+instances.) - To provision 1 or more cores, you must enter an integer
+between 1 and the maximum number of cores available for the
+infrastructure shape. For example, you can provision 2 cores or 3
+cores, but not 2.5 cores. This applies to an Autonomous Database
+Serverless instance or an Autonomous Database on Dedicated Exadata
+Infrastructure. - For Autonomous Database Serverless instances, this
+parameter is not used.
+
+For Autonomous Databases on Dedicated Exadata infrastructure, the
+maximum number of cores is determined by the infrastructure shape. See
+Characteristics of Infrastructure Shapes for shape details.
+
+**Note:** This parameter cannot be used with the *cpuCoreCount*
+parameter.
+
+--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.
+
+--private-endpoint-ip [text]
+
+The private endpoint Ip address for the resource.
+
+--private-endpoint-label [text]
+
+The resource’s private endpoint label. - Setting the endpoint label to
+a non-empty string creates a private endpoint database. - Resetting
+the endpoint label to an empty string, after the creation of the
+private endpoint database, changes the private endpoint database to a
+public endpoint database. - Setting the endpoint label to a non-empty
+string value, updates to a new private endpoint database, when the
+database is disabled and re-enabled.
+
+This setting cannot be updated in parallel with any of the following:
+licenseModel, dbEdition, cpuCoreCount, computeCount, computeModel,
+adminPassword, whitelistedIps, isMTLSConnectionRequired, dbWorkload,
+dbVersion, isRefreshable, dbName, scheduledOperations, dbToolsDetails,
+or isFreeTier.
+
+--resource-pool-leader-id [text]
+
+The unique identifier for leader autonomous database OCID OCID.
+
+--resource-pool-summary [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.
+
+--scheduled-operations [complex type]
+
+The list of scheduled operations. Consists of values such as
+dayOfWeek, scheduledStartTime, scheduledStopTime.
+
+This cannot be updated in parallel with any of the following:
+licenseModel, dbEdition, cpuCoreCount, computeCount, computeModel,
+whitelistedIps, isMTLSConnectionRequired, openMode, permissionLevel,
+dbWorkload, privateEndpointLabel, nsgIds, dbVersion, isRefreshable,
+dbName, dbToolsDetails, isLocalDataGuardEnabled, or isFreeTier.
+
+This option is a JSON list with items of type
+ScheduledOperationDetails.  For documentation on
+ScheduledOperationDetails please see our API reference: https://docs.
+cloud.oracle.com/api/#/en/database/20160918/datatypes/ScheduledOperat
+ionDetails. 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.
+
+--secret-id [text]
+
+The OCI vault secret [/Content/General/Concepts/identifiers.htm]OCID.
+
+This cannot be used in conjunction with adminPassword.
+
+--secret-version-number [integer]
+
+The version of the vault secret. If no version is specified, the
+latest version will be used.
+
+--security-attributes [complex type]
+
+Security Attributes for this resource. Each key is predefined and
+scoped to a namespace. For more information, see Resource Tags.
+Example: *{“Oracle-ZPR”: {“MaxEgressCount”: {“value”: “42”, “mode”:
+“audit”}}}* 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.
+
+--standby-whitelisted-ips [complex type]
+
+The client IP access control list (ACL). This feature is available for
+Autonomous Database Serverless  and on Exadata Cloud@Customer. Only
+clients connecting from an IP address included in the ACL may access
+the Autonomous Database instance. If *arePrimaryWhitelistedIpsUsed* is
+‘TRUE’ then Autonomous Database uses this primary’s IP access control
+list (ACL) for the disaster recovery peer called
+*standbywhitelistedips*.
+
+For Autonomous Database Serverless, this is an array of CIDR
+(classless inter-domain routing) notations for a subnet or VCN OCID
+(virtual cloud network Oracle Cloud ID). Multiple IPs and VCN OCIDs
+should be separate strings separated by commas, but if it’s other
+configurations that need multiple pieces of information then its each
+piece is connected with semicolon (;) as a delimiter. Example: *[“1.1
+.1.1”,”1.1.1.0/24”,”ocid1.vcn.oc1.sea.<unique_id>”,”ocid1.vcn.oc1.sea
+.<unique_id1>;1.1.1.1”,”ocid1.vcn.oc1.sea.<unique_id2>;1.1.0.0/16”]*
+For Exadata Cloud@Customer, this is an array of IP addresses or CIDR
+notations. Example: *[“1.1.1.1”,”1.1.1.0/24”,”1.1.2.25”]*
+
+For an update operation, if you want to delete all the IPs in the ACL,
+use an array with a single empty string entry.
+
+This cannot be updated in parallel with any of the following:
+licenseModel, dbEdition, cpuCoreCount, computeCount, computeModel,
+adminPassword, isMTLSConnectionRequired, openMode, permissionLevel,
+dbWorkload, dbVersion, isRefreshable, dbName, scheduledOperations,
+dbToolsDetails, isLocalDataGuardEnabled, or isFreeTier. 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.
+
+--subnet-id [text]
+
+The OCID of the subnet the resource is associated with.
+
+**Subnet Restrictions:** - For bare metal DB systems and for single
+node virtual machine DB systems, do not use a subnet that overlaps
+with 192.168.16.16/28. - For Exadata and virtual machine 2-node RAC
+systems, do not use a subnet that overlaps with 192.168.128.0/20. -
+For Autonomous Database, setting this will disable public secure
+access to the database.
+
+These subnets are used by the Oracle Clusterware private interconnect
+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.
+
+--subscription-id [text]
+
+The OCID of the subscription with which resource needs to be
+associated with.
+
+--vault-id [text]
+
+The OCID of the Oracle Cloud Infrastructure vault. This parameter and
+*secretId* are required for Customer Managed Keys.
+
+--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, AVAILABLE_NEEDS_ATTENTION, BACKUP_IN_PROGRESS, INACCESSIBLE, MAINTENANCE_IN_PROGRESS, PROVISIONING, RECREATING, RESTARTING, RESTORE_FAILED, RESTORE_IN_PROGRESS, ROLE_CHANGE_IN_PROGRESS, SCALE_IN_PROGRESS, STANDBY, STARTING, STOPPED, STOPPING, TERMINATED, TERMINATING, UNAVAILABLE, 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.
+
+--whitelisted-ips [complex type]
+
+The client IP access control list (ACL). This feature is available for
+Autonomous Database Serverless  and on Exadata Cloud@Customer. Only
+clients connecting from an IP address included in the ACL may access
+the Autonomous Database instance. If *arePrimaryWhitelistedIpsUsed* is
+‘TRUE’ then Autonomous Database uses this primary’s IP access control
+list (ACL) for the disaster recovery peer called
+*standbywhitelistedips*.
+
+For Autonomous Database Serverless, this is an array of CIDR
+(classless inter-domain routing) notations for a subnet or VCN OCID
+(virtual cloud network Oracle Cloud ID). Multiple IPs and VCN OCIDs
+should be separate strings separated by commas, but if it’s other
+configurations that need multiple pieces of information then its each
+piece is connected with semicolon (;) as a delimiter. Example: *[“1.1
+.1.1”,”1.1.1.0/24”,”ocid1.vcn.oc1.sea.<unique_id>”,”ocid1.vcn.oc1.sea
+.<unique_id1>;1.1.1.1”,”ocid1.vcn.oc1.sea.<unique_id2>;1.1.0.0/16”]*
+For Exadata Cloud@Customer, this is an array of IP addresses or CIDR
+notations. Example: *[“1.1.1.1”,”1.1.1.0/24”,”1.1.2.25”]*
+
+For an update operation, if you want to delete all the IPs in the ACL,
+use an array with a single empty string entry.
+
+This cannot be updated in parallel with any of the following:
+licenseModel, dbEdition, cpuCoreCount, computeCount, computeModel,
+adminPassword, isMTLSConnectionRequired, openMode, permissionLevel,
+dbWorkload, dbVersion, isRefreshable, dbName, scheduledOperations,
+dbToolsDetails, isLocalDataGuardEnabled, or isFreeTier. 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.
+
+
+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/db/autonomous-database/create-autonomous-database-gcp-key-details.html#cmdoption-compartment-id
+       export encryption_key_key_name=<substitute-value-of-encryption_key_key_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/autonomous-database/create-autonomous-database-gcp-key-details.html#cmdoption-encryption-key-key-name
+       export encryption_key_key_ring=<substitute-value-of-encryption_key_key_ring> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/autonomous-database/create-autonomous-database-gcp-key-details.html#cmdoption-encryption-key-key-ring
+       export encryption_key_location=<substitute-value-of-encryption_key_location> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/autonomous-database/create-autonomous-database-gcp-key-details.html#cmdoption-encryption-key-location
+       export encryption_key_project=<substitute-value-of-encryption_key_project> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/autonomous-database/create-autonomous-database-gcp-key-details.html#cmdoption-encryption-key-project
+
+       oci db autonomous-database create-autonomous-database-gcp-key-details --compartment-id $compartment_id --encryption-key-key-name $encryption_key_key_name --encryption-key-key-ring $encryption_key_key_ring --encryption-key-location $encryption_key_location --encryption-key-project $encryption_key_project