oci-cli 3.65.0__py3-none-any.whl → 3.65.1__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/dbmulticloud/oracle-db-azure-vault-association/update.txt

@@ -17,8 +17,8 @@
 Description
 ===========
 
-Modifies the existing Oracle DB Azure Vault Association Details for a
-given ID.
+Modifies the properties of an Oracle DB Azure Vault Association
+resource identified by the specified resource OCID.
 
 
 Usage
@@ -32,7 +32,7 @@ Required Parameters
 
 --oracle-db-azure-vault-association-id [text]
 
-The ID of the Oracle DB Azure Vault Association Resource.
+The OCID of the Oracle DB Azure Vault Association resource.
 
 
 Optional Parameters
@@ -41,7 +41,7 @@ Optional Parameters
 --compartment-id, -c [text]
 
 The OCID of the compartment that contains Oracle DB Azure Vault
-Association Resource.
+Association resource.
 
 --defined-tags [complex type]
 
@@ -63,7 +63,7 @@ via the file:// syntax.
 
 --display-name [text]
 
-Display name of Oracle DB Azure Vault Association Resource.
+Oracle DB Azure Vault Association resource name.
 
 --force
 
@@ -125,11 +125,13 @@ defined by "--wait-for-state". Defaults to 1200 seconds.
 
 --oracle-db-azure-connector-id [text]
 
-The OCID of the Oracle DB Azure Connector.
+The OCID of the Oracle DB Azure Connector that contains Oracle DB
+Azure Vault Association resource.
 
 --oracle-db-azure-vault-id [text]
 
-The OCID of the Oracle DB Azure Vault.
+The OCID of the Oracle DB Azure Vault that contains Oracle DB Azure
+Vault Association resource.
 
 --wait-for-state [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/dbmulticloud/oracle-db-azure-vault-association.txt

@@ -5,22 +5,67 @@ oracle-db-azure-vault-association
 Description
 ===========
 
-1. Oracle Azure Connector Resource: This is for installing Azure Arc
-   Server in ExaCS VM Cluster.
-
-   There are two way to install Azure Arc Server (Azure Identity) in
-   ExaCS VMCluster.
-      1. Using Bearer Access Token or
-
-      2. By providing Authentication token
-
-2. Oracle Azure Blob Container Resource: This is for to capture Azure
-   Container details and same will be used in multiple ExaCS VMCluster
-   to mount the Azure Container.
-
-3. Oracle Azure Blob Mount Resource: This is for to mount Azure
-   Container in ExaCS VMCluster using Oracle Azure Connector and
-   Oracle Azure Blob Container Resource.
+<b>Microsoft Azure:</b> <br> <b>Oracle Azure Connector
+Resource:</b>:&nbsp;&nbsp;The Oracle Azure Connector Resource is used
+to install the Azure Arc Server on an Exadata VM cluster in Oracle
+Exadata Database Service on Dedicated Infrastructure (ExaDB-D).
+
+   The supported method to install the Azure Arc Server (Azure
+   Identity) on the Exadata VM cluster:
+
+<ul>
+   <li>Using a Bearer Access Token</li>
+
+</ul>
+
+<b>Oracle Azure Blob Container Resource:</b>&nbsp;&nbsp;The Oracle
+Azure Blob Container Resource is used to capture the details of an
+Azure Blob Container. This resource can then be reused across multiple
+Exadata VM clusters in Oracle Exadata Database Service on Dedicated
+Infrastructure (ExaDB-D) to mount the Azure container.
+
+<b>Oracle Azure Blob Mount Resource:</b>&nbsp;&nbsp;The Oracle Azure
+Blob Mount Resource is used to mount an Azure Blob Container on an
+Exadata VM cluster in Oracle Exadata Database Service on Dedicated
+Infrastructure (ExaDB-D). It relies on both the Oracle Azure Connector
+and the Oracle Azure Blob Container Resource to perform the mount
+operation.
+
+<b>Discover Azure Vaults and Keys Resource:</b>&nbsp;&nbsp;The
+Discover Oracle Azure Vaults and Azure Keys Resource is used to
+discover Azure Vaults and the associated encryption keys available in
+your Azure project.
+
+<b>Oracle Azure Vault:</b>&nbsp;&nbsp;The Oracle Azure Vault Resource
+is used to manage Azure Vaults within Oracle Cloud Infrastructure
+(OCI) for use with services such as Oracle Exadata Database Service on
+Dedicated Infrastructure.
+
+<b>Oracle Azure Key:</b>&nbsp;&nbsp;Oracle Azure Key Resource is used
+to register and manage a Oracle Azure Key Key within Oracle Cloud
+Infrastructure (OCI) under an associated Azure Vault.
+
+<br>
+
+<b>Google Cloud:</b><br> <b>Oracle Google Cloud Connector
+Resource:</b>&nbsp;&nbsp;The Oracle Google Cloud Connector Resource is
+used to install the Google Cloud Identity Connector on an Exadata VM
+cluster in Oracle Exadata Database Service on Dedicated Infrastructure
+(ExaDB-D).
+
+<b>Discover Google Key Rings and Keys Resource:</b>&nbsp;&nbsp;The
+Discover Google Key Rings and Keys Resource is used to discover Google
+Cloud Key Rings and the associated encryption keys available in your
+Google Cloud project.
+
+<b>Google Key Rings Resource:</b>&nbsp;&nbsp;The Google Key Rings
+Resource is used to register and manage Google Cloud Key Rings within
+Oracle Cloud Infrastructure (OCI) for use with services such as Oracle
+Exadata Database Service on Dedicated Infrastructure.
+
+<b>Google Key Resource:</b>&nbsp;&nbsp;The Google Key Resource is used
+to register and manage a Google Cloud Key within Oracle Cloud
+Infrastructure (OCI) under an associated Google Key Ring.
 
 
 Available Commands

oci_cli/help_text_producer/data_files/text/cmdref/dbmulticloud/oracle-db-azure-vault.txt

@@ -5,22 +5,67 @@ oracle-db-azure-vault
 Description
 ===========
 
-1. Oracle Azure Connector Resource: This is for installing Azure Arc
-   Server in ExaCS VM Cluster.
-
-   There are two way to install Azure Arc Server (Azure Identity) in
-   ExaCS VMCluster.
-      1. Using Bearer Access Token or
-
-      2. By providing Authentication token
-
-2. Oracle Azure Blob Container Resource: This is for to capture Azure
-   Container details and same will be used in multiple ExaCS VMCluster
-   to mount the Azure Container.
-
-3. Oracle Azure Blob Mount Resource: This is for to mount Azure
-   Container in ExaCS VMCluster using Oracle Azure Connector and
-   Oracle Azure Blob Container Resource.
+<b>Microsoft Azure:</b> <br> <b>Oracle Azure Connector
+Resource:</b>:&nbsp;&nbsp;The Oracle Azure Connector Resource is used
+to install the Azure Arc Server on an Exadata VM cluster in Oracle
+Exadata Database Service on Dedicated Infrastructure (ExaDB-D).
+
+   The supported method to install the Azure Arc Server (Azure
+   Identity) on the Exadata VM cluster:
+
+<ul>
+   <li>Using a Bearer Access Token</li>
+
+</ul>
+
+<b>Oracle Azure Blob Container Resource:</b>&nbsp;&nbsp;The Oracle
+Azure Blob Container Resource is used to capture the details of an
+Azure Blob Container. This resource can then be reused across multiple
+Exadata VM clusters in Oracle Exadata Database Service on Dedicated
+Infrastructure (ExaDB-D) to mount the Azure container.
+
+<b>Oracle Azure Blob Mount Resource:</b>&nbsp;&nbsp;The Oracle Azure
+Blob Mount Resource is used to mount an Azure Blob Container on an
+Exadata VM cluster in Oracle Exadata Database Service on Dedicated
+Infrastructure (ExaDB-D). It relies on both the Oracle Azure Connector
+and the Oracle Azure Blob Container Resource to perform the mount
+operation.
+
+<b>Discover Azure Vaults and Keys Resource:</b>&nbsp;&nbsp;The
+Discover Oracle Azure Vaults and Azure Keys Resource is used to
+discover Azure Vaults and the associated encryption keys available in
+your Azure project.
+
+<b>Oracle Azure Vault:</b>&nbsp;&nbsp;The Oracle Azure Vault Resource
+is used to manage Azure Vaults within Oracle Cloud Infrastructure
+(OCI) for use with services such as Oracle Exadata Database Service on
+Dedicated Infrastructure.
+
+<b>Oracle Azure Key:</b>&nbsp;&nbsp;Oracle Azure Key Resource is used
+to register and manage a Oracle Azure Key Key within Oracle Cloud
+Infrastructure (OCI) under an associated Azure Vault.
+
+<br>
+
+<b>Google Cloud:</b><br> <b>Oracle Google Cloud Connector
+Resource:</b>&nbsp;&nbsp;The Oracle Google Cloud Connector Resource is
+used to install the Google Cloud Identity Connector on an Exadata VM
+cluster in Oracle Exadata Database Service on Dedicated Infrastructure
+(ExaDB-D).
+
+<b>Discover Google Key Rings and Keys Resource:</b>&nbsp;&nbsp;The
+Discover Google Key Rings and Keys Resource is used to discover Google
+Cloud Key Rings and the associated encryption keys available in your
+Google Cloud project.
+
+<b>Google Key Rings Resource:</b>&nbsp;&nbsp;The Google Key Rings
+Resource is used to register and manage Google Cloud Key Rings within
+Oracle Cloud Infrastructure (OCI) for use with services such as Oracle
+Exadata Database Service on Dedicated Infrastructure.
+
+<b>Google Key Resource:</b>&nbsp;&nbsp;The Google Key Resource is used
+to register and manage a Google Cloud Key within Oracle Cloud
+Infrastructure (OCI) under an associated Google Key Ring.
 
 
 Available Commands

oci_cli/help_text_producer/data_files/text/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/change-compartment.txt

@@ -0,0 +1,132 @@
+"change-compartment"
+********************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Moves the Oracle DB GCP Identity Connector resource into a different
+compartment. When provided, ‘If-Match’ is checked against ‘ETag’
+values of the resource.
+
+
+Usage
+=====
+
+   oci dbmulticloud oracle-db-gcp-identity-connector change-compartment [OPTIONS]
+
+
+Required Parameters
+===================
+
+--oracle-db-gcp-identity-connector-id [text]
+
+The OCID of the Oracle DB GCP Identity Configuration Resource.
+
+
+Optional Parameters
+===================
+
+--compartment-id, -c [text]
+
+The OCID of the compartment that contains the Oracle DB GCP Identity
+Connector resource.
+
+--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 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 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 oracle_db_gcp_identity_connector_id=<substitute-value-of-oracle_db_gcp_identity_connector_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/change-compartment.html#cmdoption-oracle-db-gcp-identity-connector-id
+
+       oci dbmulticloud oracle-db-gcp-identity-connector change-compartment --oracle-db-gcp-identity-connector-id $oracle_db_gcp_identity_connector_id

oci_cli/help_text_producer/data_files/text/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/create.txt

@@ -0,0 +1,195 @@
+"create"
+********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Creates Oracle DB GCP Identity Connector resource.
+
+
+Usage
+=====
+
+   oci dbmulticloud oracle-db-gcp-identity-connector create [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+The OCID of the compartment that contains the Oracle DB GCP Identity
+Connector resource.
+
+--display-name [text]
+
+Oracle DB Google GCP Identity Connector resource name.
+
+--gcp-location [text]
+
+GCP Location.
+
+--gcp-resource-service-agent-id [text]
+
+The ID of the GCP resource service agent.
+
+--gcp-workload-identity-pool-id [text]
+
+The ID of the cloud GCP Workload Identity Pool.
+
+--gcp-workload-identity-provider-id [text]
+
+The ID of the GCP Workload Identity Provider.
+
+--issuer-url [text]
+
+OIDC token issuer Url
+
+--project-id [text]
+
+Project id of the customer project.
+
+--resource-id [text]
+
+The OCID of the GCP VM Cluster resource.
+
+
+Optional Parameters
+===================
+
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. For more information, see Resource Tags.
+
+Example:
+
+   {"Operations": {"CostCenter": "42"}}
+
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
+--freeform-tags [complex type]
+
+Free-form tags for this resource. Each tag is a simple key-value pair
+with no predefined name, type, or namespace. For more information, see
+Resource Tags.
+
+Example:
+
+   {"Department": "Finance"}
+
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
+--from-json [text]
+
+Provide input to this command as a JSON document from a file using the
+file://path-to/file syntax.
+
+The "--generate-full-command-json-input" option can be used to
+generate a sample json file to be used with this command option. The
+key names are pre-populated and match the command option names
+(converted to camelCase format, e.g. compartment-id –> compartmentId),
+while the values of the keys need to be populated by the user before
+using the sample file as an input to this command. For any command
+option that accepts multiple values, the value of the key can be a
+JSON array.
+
+Options can still be provided on the command line. If an option exists
+in both the JSON document and the command line then the command line
+specified value will be used.
+
+For examples on usage of this option, please see our “using CLI with
+advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--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 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/dbmulticloud/oracle-db-gcp-identity-connector/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/dbmulticloud/oracle-db-gcp-identity-connector/create.html#cmdoption-display-name
+       export gcp_location=<substitute-value-of-gcp_location> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/create.html#cmdoption-gcp-location
+       export gcp_resource_service_agent_id=<substitute-value-of-gcp_resource_service_agent_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/create.html#cmdoption-gcp-resource-service-agent-id
+       export gcp_workload_identity_pool_id=<substitute-value-of-gcp_workload_identity_pool_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/create.html#cmdoption-gcp-workload-identity-pool-id
+       export gcp_workload_identity_provider_id=<substitute-value-of-gcp_workload_identity_provider_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/create.html#cmdoption-gcp-workload-identity-provider-id
+       export issuer_url=<substitute-value-of-issuer_url> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/create.html#cmdoption-issuer-url
+       export project_id=<substitute-value-of-project_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/create.html#cmdoption-project-id
+       export resource_id=<substitute-value-of-resource_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/create.html#cmdoption-resource-id
+
+       oci dbmulticloud oracle-db-gcp-identity-connector create --compartment-id $compartment_id --display-name $display_name --gcp-location $gcp_location --gcp-resource-service-agent-id $gcp_resource_service_agent_id --gcp-workload-identity-pool-id $gcp_workload_identity_pool_id --gcp-workload-identity-provider-id $gcp_workload_identity_provider_id --issuer-url $issuer_url --project-id $project_id --resource-id $resource_id

oci_cli/help_text_producer/data_files/text/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/delete.txt

@@ -0,0 +1,130 @@
+"delete"
+********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Deletes the Oracle DB GCP Identity Connector resource and removes the
+associated connector from the database resource.
+
+
+Usage
+=====
+
+   oci dbmulticloud oracle-db-gcp-identity-connector delete [OPTIONS]
+
+
+Required Parameters
+===================
+
+--oracle-db-gcp-identity-connector-id [text]
+
+The OCID of the Oracle DB GCP Identity Configuration Resource.
+
+
+Optional Parameters
+===================
+
+--force
+
+Perform deletion without prompting for confirmation.
+
+--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 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 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 oracle_db_gcp_identity_connector_id=<substitute-value-of-oracle_db_gcp_identity_connector_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dbmulticloud/oracle-db-gcp-identity-connector/delete.html#cmdoption-oracle-db-gcp-identity-connector-id
+
+       oci dbmulticloud oracle-db-gcp-identity-connector delete --oracle-db-gcp-identity-connector-id $oracle_db_gcp_identity_connector_id