oci-cli 3.62.0__py3-none-any.whl → 3.62.1__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/opsi/database-insights/change-macs-managed-cloud-database-insight-connection-credential-by-named-credentials.txt

@@ -0,0 +1,158 @@
+"change-macs-managed-cloud-database-insight-connection-credential-by-named-credentials"
+***************************************************************************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Change the connection details of a Cloud MACS-managed database
+insight. When provided, If-Match is checked against ETag values of the
+resource.
+
+
+Usage
+=====
+
+   oci opsi database-insights change-macs-managed-cloud-database-insight-connection-credential-by-named-credentials [OPTIONS]
+
+
+Required Parameters
+===================
+
+--connection-details [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.
+
+--database-insight-id [text]
+
+Unique database insight identifier
+
+--management-agent-id [text]
+
+The OCID of the Management Agent
+
+
+Optional Parameters
+===================
+
+--connection-credential-details-credential-source-name [text]
+
+Credential source name that had been added in Management Agent wallet.
+This value is only required when Credential set by
+CREDENTIALS_BY_SOURCE and is optional properties for ther others.
+
+--connection-credential-details-named-credential-id [text]
+
+The credential OCID stored in management agent.
+
+--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]
+
+Used for optimistic concurrency control. In the update or delete call
+for a resource, set the *if-match* parameter to the value of the etag
+from a previous get, create, or update 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, SUCCEEDED, WAITING
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the work request
+has reached the state defined by "--wait-for-state". Defaults to 30
+seconds.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
+
+
+Example using required parameter
+================================
+
+Copy and paste the following example into a JSON file, replacing the
+example parameters with your own.
+
+       oci opsi database-insights change-macs-managed-cloud-database-insight-connection-credential-by-named-credentials --generate-param-json-input connection-details > connection-details.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 database_insight_id=<substitute-value-of-database_insight_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/change-macs-managed-cloud-database-insight-connection-credential-by-named-credentials.html#cmdoption-database-insight-id
+       export management_agent_id=<substitute-value-of-management_agent_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/change-macs-managed-cloud-database-insight-connection-credential-by-named-credentials.html#cmdoption-management-agent-id
+
+       oci opsi database-insights change-macs-managed-cloud-database-insight-connection-credential-by-named-credentials --connection-details file://connection-details.json --database-insight-id $database_insight_id --management-agent-id $management_agent_id

oci_cli/help_text_producer/data_files/text/cmdref/opsi/database-insights/change-pe-comanaged-database-detail.txt

@@ -30,11 +30,6 @@ Usage
 Required Parameters
 ===================
 
---credential-details-credential-source-name [text]
-
-Credential source name that had been added in Management Agent wallet.
-This is supplied in the External Database Service.
-
 --database-insight-id [text]
 
 Unique database insight identifier
@@ -62,6 +57,12 @@ 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.
 
+--credential-details-credential-source-name [text]
+
+Credential source name that had been added in Management Agent wallet.
+This value is only required when Credential set by
+CREDENTIALS_BY_SOURCE and is optional properties for ther others.
+
 --credential-details-password-secret-id [text]
 
 The secret OCID mapping to the database credentials.
@@ -171,10 +172,9 @@ security policies before trying the examples.
        export is_used_for_rac_dbs=<substitute-value-of-is_used_for_rac_dbs> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/opsi-private-endpoint/create.html#cmdoption-is-used-for-rac-dbs
        export subnet_id=<substitute-value-of-subnet_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/opsi-private-endpoint/create.html#cmdoption-subnet-id
        export vcn_id=<substitute-value-of-vcn_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/opsi-private-endpoint/create.html#cmdoption-vcn-id
-       export credential_details_credential_source_name=<substitute-value-of-credential_details_credential_source_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/change-pe-comanaged-database-detail.html#cmdoption-credential-details-credential-source-name
        export database_insight_id=<substitute-value-of-database_insight_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/change-pe-comanaged-database-detail.html#cmdoption-database-insight-id
        export service_name=<substitute-value-of-service_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/change-pe-comanaged-database-detail.html#cmdoption-service-name
 
        opsi_private_endpoint_id=$(oci opsi opsi-private-endpoint create --compartment-id $compartment_id --display-name $display_name --is-used-for-rac-dbs $is_used_for_rac_dbs --subnet-id $subnet_id --vcn-id $vcn_id --query data.id --raw-output)
 
-       oci opsi database-insights change-pe-comanaged-database-detail --credential-details-credential-source-name $credential_details_credential_source_name --database-insight-id $database_insight_id --opsi-private-endpoint-id $opsi_private_endpoint_id --service-name $service_name
+       oci opsi database-insights change-pe-comanaged-database-detail --database-insight-id $database_insight_id --opsi-private-endpoint-id $opsi_private_endpoint_id --service-name $service_name

oci_cli/help_text_producer/data_files/text/cmdref/opsi/database-insights/create-macs-managed-autonomous-database-insight.txt

@@ -0,0 +1,210 @@
+"create-macs-managed-autonomous-database-insight"
+*************************************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Create a Database Insight resource for a database in Operations
+Insights. The database will be enabled in Operations Insights.
+Database metric collection and analysis will be started.
+
+
+Usage
+=====
+
+   oci opsi database-insights create-macs-managed-autonomous-database-insight [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+Compartment Identifier of database
+
+--connection-credential-details [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.
+
+--connection-details [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.
+
+--database-id [text]
+
+The OCID of the database.
+
+--database-resource-type [text]
+
+OCI database resource type
+
+--deployment-type [text]
+
+Database Deployment Type
+
+Accepted values are:
+
+   EXACC
+
+--management-agent-id [text]
+
+The OCID of the Management Agent
+
+
+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
+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.
+
+--system-tags [complex type]
+
+System tags for this resource. Each key is predefined and scoped to a
+namespace. Example: *{“orcl-cloud”: {“free-tier-retained”: “true”}}*
+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.
+
+--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, SUCCEEDED, WAITING
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the work request
+has reached the state defined by "--wait-for-state". Defaults to 30
+seconds.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
+
+
+Example using required parameter
+================================
+
+Copy and paste the following example into a JSON file, replacing the
+example parameters with your own.
+
+       oci opsi database-insights create-macs-managed-autonomous-database-insight --generate-param-json-input connection-credential-details > connection-credential-details.json
+       oci opsi database-insights create-macs-managed-autonomous-database-insight --generate-param-json-input connection-details > connection-details.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/opsi/database-insights/create-macs-managed-autonomous-database-insight.html#cmdoption-compartment-id
+       export database_id=<substitute-value-of-database_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/create-macs-managed-autonomous-database-insight.html#cmdoption-database-id
+       export database_resource_type=<substitute-value-of-database_resource_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/create-macs-managed-autonomous-database-insight.html#cmdoption-database-resource-type
+       export deployment_type=<substitute-value-of-deployment_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/create-macs-managed-autonomous-database-insight.html#cmdoption-deployment-type
+       export management_agent_id=<substitute-value-of-management_agent_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/create-macs-managed-autonomous-database-insight.html#cmdoption-management-agent-id
+
+       oci opsi database-insights create-macs-managed-autonomous-database-insight --compartment-id $compartment_id --connection-credential-details file://connection-credential-details.json --connection-details file://connection-details.json --database-id $database_id --database-resource-type $database_resource_type --deployment-type $deployment_type --management-agent-id $management_agent_id

oci_cli/help_text_producer/data_files/text/cmdref/opsi/database-insights/enable-autonomous-database-insight-advanced-features-credential-by-iam.txt

@@ -42,11 +42,6 @@ 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.
 
---credential-details-credential-source-name [text]
-
-Credential source name that had been added in Management Agent wallet.
-This is supplied in the External Database Service.
-
 --database-insight-id [text]
 
 Unique database insight identifier
@@ -55,6 +50,12 @@ Unique database insight identifier
 Optional Parameters
 ===================
 
+--credential-details-credential-source-name [text]
+
+Credential source name that had been added in Management Agent wallet.
+This value is only required when Credential set by
+CREDENTIALS_BY_SOURCE and is optional properties for ther others.
+
 --from-json [text]
 
 Provide input to this command as a JSON document from a file using the
@@ -147,7 +148,6 @@ 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 credential_details_credential_source_name=<substitute-value-of-credential_details_credential_source_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/enable-autonomous-database-insight-advanced-features-credential-by-iam.html#cmdoption-credential-details-credential-source-name
        export database_insight_id=<substitute-value-of-database_insight_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/enable-autonomous-database-insight-advanced-features-credential-by-iam.html#cmdoption-database-insight-id
 
-       oci opsi database-insights enable-autonomous-database-insight-advanced-features-credential-by-iam --connection-details file://connection-details.json --credential-details-credential-source-name $credential_details_credential_source_name --database-insight-id $database_insight_id
+       oci opsi database-insights enable-autonomous-database-insight-advanced-features-credential-by-iam --connection-details file://connection-details.json --database-insight-id $database_insight_id

oci_cli/help_text_producer/data_files/text/cmdref/opsi/database-insights/enable-autonomous-database-insight-advanced-features-credential-by-vault.txt

@@ -42,11 +42,6 @@ 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.
 
---credential-source-name [text]
-
-Credential source name that had been added in Management Agent wallet.
-This is supplied in the External Database Service.
-
 --database-insight-id [text]
 
 Unique database insight identifier
@@ -168,7 +163,6 @@ 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 credential_source_name=<substitute-value-of-credential_source_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/enable-autonomous-database-insight-advanced-features-credential-by-vault.html#cmdoption-credential-source-name
        export database_insight_id=<substitute-value-of-database_insight_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/enable-autonomous-database-insight-advanced-features-credential-by-vault.html#cmdoption-database-insight-id
 
-       oci opsi database-insights enable-autonomous-database-insight-advanced-features-credential-by-vault --connection-details file://connection-details.json --credential-source-name $credential_source_name --database-insight-id $database_insight_id
+       oci opsi database-insights enable-autonomous-database-insight-advanced-features-credential-by-vault --connection-details file://connection-details.json --database-insight-id $database_insight_id

oci_cli/help_text_producer/data_files/text/cmdref/opsi/database-insights/enable-macs-managed-autonomous-database-insight.txt

@@ -0,0 +1,203 @@
+"enable-macs-managed-autonomous-database-insight"
+*************************************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Enables a database in Operations Insights. Database metric collection
+and analysis will be started.
+
+
+Usage
+=====
+
+   oci opsi database-insights enable-macs-managed-autonomous-database-insight [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+The compartment OCID of the Autonomous Database.
+
+--connection-credential-details [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.
+
+--connection-details [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.
+
+--database-insight-id [text]
+
+Unique database insight identifier
+
+--management-agent-id [text]
+
+The OCID of the Management Agent
+
+
+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
+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]
+
+Used for optimistic concurrency control. In the update or delete call
+for a resource, set the *if-match* parameter to the value of the etag
+from a previous get, create, or update 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.
+
+--system-tags [complex type]
+
+System tags for this resource. Each key is predefined and scoped to a
+namespace. Example: *{“orcl-cloud”: {“free-tier-retained”: “true”}}*
+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.
+
+--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, SUCCEEDED, WAITING
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the work request
+has reached the state defined by "--wait-for-state". Defaults to 30
+seconds.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
+
+
+Example using required parameter
+================================
+
+Copy and paste the following example into a JSON file, replacing the
+example parameters with your own.
+
+       oci opsi database-insights enable-macs-managed-autonomous-database-insight --generate-param-json-input connection-credential-details > connection-credential-details.json
+       oci opsi database-insights enable-macs-managed-autonomous-database-insight --generate-param-json-input connection-details > connection-details.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/opsi/database-insights/enable-macs-managed-autonomous-database-insight.html#cmdoption-compartment-id
+       export database_insight_id=<substitute-value-of-database_insight_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/enable-macs-managed-autonomous-database-insight.html#cmdoption-database-insight-id
+       export management_agent_id=<substitute-value-of-management_agent_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/opsi/database-insights/enable-macs-managed-autonomous-database-insight.html#cmdoption-management-agent-id
+
+       oci opsi database-insights enable-macs-managed-autonomous-database-insight --compartment-id $compartment_id --connection-credential-details file://connection-credential-details.json --connection-details file://connection-details.json --database-insight-id $database_insight_id --management-agent-id $management_agent_id

oci_cli/help_text_producer/data_files/text/cmdref/opsi/database-insights/list-database-configurations.txt

@@ -61,7 +61,7 @@ ADW-D, ATP-D, EXTERNAL-PDB, EXTERNAL-NONCDB.
 
 Accepted values are:
 
-   ADW-D, ADW-S, ATP-D, ATP-S, COMANAGED-BM-CDB, COMANAGED-BM-NONCDB, COMANAGED-BM-PDB, COMANAGED-EXACC-CDB, COMANAGED-EXACC-NONCDB, COMANAGED-EXACC-PDB, COMANAGED-EXACS-CDB, COMANAGED-EXACS-NONCDB, COMANAGED-EXACS-PDB, COMANAGED-VM-CDB, COMANAGED-VM-NONCDB, COMANAGED-VM-PDB, EXTERNAL-MYSQL, EXTERNAL-NONCDB, EXTERNAL-PDB, MDS-MYSQL
+   ADW-D, ADW-EXACC, ADW-S, ATP-D, ATP-EXACC, ATP-S, COMANAGED-BM-CDB, COMANAGED-BM-NONCDB, COMANAGED-BM-PDB, COMANAGED-EXACC-CDB, COMANAGED-EXACC-NONCDB, COMANAGED-EXACC-PDB, COMANAGED-EXACS-CDB, COMANAGED-EXACS-NONCDB, COMANAGED-EXACS-PDB, COMANAGED-VM-CDB, COMANAGED-VM-NONCDB, COMANAGED-VM-PDB, EXTERNAL-ADW, EXTERNAL-ATP, EXTERNAL-MYSQL, EXTERNAL-NONCDB, EXTERNAL-PDB, MDS-MYSQL
 
 --defined-tag-equals [text]