oci-cli 3.63.3__py3-none-any.whl → 3.64.1__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/security-policy-entry-state/list.txt

@@ -51,7 +51,7 @@ The current state of the security policy deployment.
 
 Accepted values are:
 
-   CONFLICT, CREATED, DELETED, MODIFIED, UNAUTHORIZED
+   CONFLICT, CONNECTIVITY_ISSUE, CREATED, DELETED, MODIFIED, UNAUTHORIZED, UNKNOWN_ERROR, UNSUPPORTED_SYNTAX
 
 --from-json [text]
 
@@ -98,6 +98,19 @@ valid when used with "--all" or "--limit", and ignored otherwise.
 An optional filter to return only resources that match the specified
 security policy entry OCID.
 
+--security-policy-entry-type [text]
+
+The type of the security policy deployment.
+
+Accepted values are:
+
+   AUDIT_POLICY, CONFIG, FIREWALL_POLICY
+
+--target-id [text]
+
+An optional filter to return only resources that match the specified
+target id.
+
 
 Global Parameters
 =================
@@ -125,6 +138,12 @@ 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 security_policy_deployment_id=<substitute-value-of-security_policy_deployment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/data-safe/security-policy-entry-state/list.html#cmdoption-security-policy-deployment-id
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/data-safe/security-policy/create.html#cmdoption-compartment-id
+       export target_id=<substitute-value-of-target_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/data-safe/security-policy-deployment/create.html#cmdoption-target-id
+       export target_type=<substitute-value-of-target_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/data-safe/security-policy-deployment/create.html#cmdoption-target-type
+
+       security_policy_id=$(oci data-safe security-policy create --compartment-id $compartment_id --query data.id --raw-output)
+
+       security_policy_deployment_id=$(oci data-safe security-policy-deployment create --compartment-id $compartment_id --security-policy-id $security_policy_id --target-id $target_id --target-type $target_type --query data.id --raw-output)
 
        oci data-safe security-policy-entry-state list --security-policy-deployment-id $security_policy_deployment_id

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/security-policy.txt

@@ -14,6 +14,10 @@ Available Commands
 
 * change-compartment
 
+* create
+
+* delete
+
 * get
 
 * list

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/sensitive-data-model/list-discovery-analytics.txt

@@ -111,11 +111,38 @@ valid when used with "--all" or "--limit", and ignored otherwise.
 A filter to return only the resources that match the specified
 sensitive data model OCID.
 
+--sensitive-type-group-id [text]
+
+An optional filter to return only resources that match the specified
+OCID of the sensitive type group resource.
+
 --sensitive-type-id [text]
 
 A filter to return only items related to a specific sensitive type
 OCID.
 
+--sort-by [text]
+
+The field to sort by. You can specify only one sorting parameter
+(sortOrder). The default order for all the fields is ascending.
+
+Accepted values are:
+
+   timeLastDiscovered
+
+--sort-order [text]
+
+The sort order to use, either ascending (ASC) or descending (DESC).
+
+Accepted values are:
+
+   ASC, DESC
+
+--target-database-group-id [text]
+
+A filter to return the target database group that matches the
+specified OCID.
+
 --target-id [text]
 
 A filter to return only items related to a specific target OCID.

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/sensitive-data-model/list-sensitive-column-analytics.txt

@@ -151,6 +151,11 @@ OCID of the sensitive type group resource.
 A filter to return only the sensitive columns that are associated with
 one of the sensitive types identified by the specified OCIDs.
 
+--target-database-group-id [text]
+
+A filter to return the target database group that matches the
+specified OCID.
+
 --target-id [text]
 
 A filter to return only items related to a specific target OCID.

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/sql-collection/list.txt

@@ -158,6 +158,11 @@ Accepted values are:
 An optional filter to return only resources that match the specified
 OCID of the SQL collection resource.
 
+--target-database-group-id [text]
+
+A filter to return the target database group that matches the
+specified OCID.
+
 --target-id [text]
 
 A filter to return only items related to a specific target OCID.

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/sql-collection-analytics/list.txt

@@ -134,6 +134,11 @@ Pagination.
 When fetching results, the number of results to fetch per call. Only
 valid when used with "--all" or "--limit", and ignored otherwise.
 
+--target-database-group-id [text]
+
+A filter to return the target database group that matches the
+specified OCID.
+
 --target-id [text]
 
 A filter to return only items related to a specific target OCID.

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/sql-firewall-allowed-sql/list.txt

@@ -127,7 +127,7 @@ RFC3339. In SCIM filtering expressions, text, date, and time values
 must be enclosed in quotation marks, with date and time values using
 ISO-8601 format. (Numeric and boolean values should not be quoted.)
 
-**Example:** query=(currentUser eq ‘SCOTT’) and (topLevel eq ‘YES’)
+**Example:** query=(currentUser eq “SCOTT”) and (topLevel eq “YES”)
 
 --sort-by [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/sql-firewall-allowed-sql-analytics/list.txt

@@ -137,7 +137,7 @@ RFC3339. In SCIM filtering expressions, text, date, and time values
 must be enclosed in quotation marks, with date and time values using
 ISO-8601 format. (Numeric and boolean values should not be quoted.)
 
-**Example:** query=(currentUser eq ‘SCOTT’) and (topLevel eq ‘YES’)
+**Example:** query=(currentUser eq “SCOTT”) and (topLevel eq “YES”)
 
 
 Global Parameters

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/sql-firewall-violation-summary/list-sql-firewall-violation-analytics.txt

@@ -126,8 +126,8 @@ RFC3339. In SCIM filtering expressions, text, date, and time values
 must be enclosed in quotation marks, with date and time values using
 ISO-8601 format. (Numeric and boolean values should not be quoted.)
 
-**Example:** query=(operationTime ge ‘2021-06-04T01-00-26’) and
-(violationAction eq ‘BLOCKED’)
+**Example:** query=(operationTime ge “2021-06-04T01:00:26.000Z”) and
+(violationAction eq “BLOCKED”)
 
 --sort-by [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/sql-firewall-violation-summary/list-sql-firewall-violations.txt

@@ -111,8 +111,8 @@ RFC3339. In SCIM filtering expressions, text, date, and time values
 must be enclosed in quotation marks, with date and time values using
 ISO-8601 format. (Numeric and boolean values should not be quoted.)
 
-**Example:** query=(operationTime ge ‘2021-06-04T01-00-26’) and
-(violationAction eq ‘BLOCKED’)
+**Example:** query=(operationTime ge “2021-06-04T01:00:26.000Z”) and
+(violationAction eq “BLOCKED”)
 
 --sort-by [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/target-database-group/change-compartment.txt

@@ -0,0 +1,138 @@
+"change-compartment"
+********************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Moves the target database group to the specified compartment.
+
+
+Usage
+=====
+
+   oci data-safe target-database-group change-compartment [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+The OCID of the compartment to which the target database group should
+be moved.
+
+--target-database-group-id [text]
+
+The OCID of the specified target database group.
+
+
+Optional Parameters
+===================
+
+--from-json [text]
+
+Provide input to this command as a JSON document from a file using the
+file://path-to/file syntax.
+
+The "--generate-full-command-json-input" option can be used to
+generate a sample json file to be used with this command option. The
+key names are pre-populated and match the command option names
+(converted to camelCase format, e.g. compartment-id –> compartmentId),
+while the values of the keys need to be populated by the user before
+using the sample file as an input to this command. For any command
+option that accepts multiple values, the value of the key can be a
+JSON array.
+
+Options can still be provided on the command line. If an option exists
+in both the JSON document and the command line then the command line
+specified value will be used.
+
+For examples on usage of this option, please see our “using CLI with
+advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--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, SUCCEEDED, SUSPENDED, SUSPENDING
+
+--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 data-safe target-database-group create --generate-param-json-input matching-criteria > matching-criteria.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/data-safe/target-database-group/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/data-safe/target-database-group/create.html#cmdoption-display-name
+
+       target_database_group_id=$(oci data-safe target-database-group create --compartment-id $compartment_id --display-name $display_name --matching-criteria file://matching-criteria.json --query data.id --raw-output)
+
+       oci data-safe target-database-group change-compartment --compartment-id $compartment_id --target-database-group-id $target_database_group_id

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/target-database-group/create.txt

@@ -0,0 +1,175 @@
+"create"
+********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Creates a new target database group.
+
+
+Usage
+=====
+
+   oci data-safe target-database-group create [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+The OCID of the compartment to create the target database group.
+
+--display-name [text]
+
+The name of the target database group.
+
+--matching-criteria [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.
+
+
+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.
+
+--description [text]
+
+Description of the target database group (optional).
+
+--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, SUCCEEDED, SUSPENDED, SUSPENDING
+
+--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 data-safe target-database-group create --generate-param-json-input matching-criteria > matching-criteria.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/data-safe/target-database-group/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/data-safe/target-database-group/create.html#cmdoption-display-name
+
+       oci data-safe target-database-group create --compartment-id $compartment_id --display-name $display_name --matching-criteria file://matching-criteria.json

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/target-database-group/delete.txt

@@ -0,0 +1,137 @@
+"delete"
+********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Deletes the specified target database group.
+
+
+Usage
+=====
+
+   oci data-safe target-database-group delete [OPTIONS]
+
+
+Required Parameters
+===================
+
+--target-database-group-id [text]
+
+The OCID of the specified target database group.
+
+
+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, SUCCEEDED, SUSPENDED, SUSPENDING
+
+--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 data-safe target-database-group create --generate-param-json-input matching-criteria > matching-criteria.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/data-safe/target-database-group/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/data-safe/target-database-group/create.html#cmdoption-display-name
+
+       target_database_group_id=$(oci data-safe target-database-group create --compartment-id $compartment_id --display-name $display_name --matching-criteria file://matching-criteria.json --query data.id --raw-output)
+
+       oci data-safe target-database-group delete --target-database-group-id $target_database_group_id