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/audit-trail/update.txt

@@ -37,6 +37,12 @@ The OCID of the audit trail.
 Optional Parameters
 ===================
 
+--can-update-last-archive-time-on-target [boolean]
+
+Indicates if the Datasafe updates last archive time on target
+database. If isAutoPurgeEnabled field is enabled, this field must be
+true.
+
 --defined-tags [complex type]
 
 Defined tags for this resource. Each key is predefined and scoped to a

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/audit-trail-analytic-collection/list-audit-trail-analytics.txt

@@ -126,10 +126,197 @@ Pagination.
 When fetching results, the number of results to fetch per call. Only
 valid when used with "--all" or "--limit", and ignored otherwise.
 
+--query-time-zone [text]
+
+Default time zone is UTC if no time zone provided. The date-time
+considerations of the resource will be in accordance with the
+specified time zone.
+
+--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.
 
+--time-ended [datetime]
+
+An optional filter to return audit events whose creation time in the
+database is less than and equal to the date-time specified, in the
+format defined by RFC3339.
+
+   The following datetime formats are supported:
+
+
+UTC with microseconds
+---------------------
+
+   Format: YYYY-MM-DDTHH:mm:ss.ssssssTZD
+   Example: 2017-09-15T20:30:00.123456Z
+
+   UTC with milliseconds
+   ***********************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ss.sssTZD
+       Example: 2017-09-15T20:30:00.123Z
+
+   UTC without milliseconds
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T20:30:00Z
+
+   UTC with minute precision
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T20:30Z
+
+
+Timezone with microseconds
+--------------------------
+
+   Format: YYYY-MM-DDTHH:mm:ssTZD
+   Example: 2017-09-15T12:30:00.456789-08:00, 2017-09-15T12:30:00.456789-0800
+
+   Timezone with milliseconds
+   ***************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00.456-08:00, 2017-09-15T12:30:00.456-0800
+
+   Timezone without milliseconds
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00-08:00, 2017-09-15T12:30:00-0800
+
+   Timezone with minute precision
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T12:30-08:00, 2017-09-15T12:30-0800
+
+   Short date and time
+   ********************
+   The timezone for this date and time will be taken as UTC (Needs to be surrounded by single or double quotes)
+
+   .. code::
+
+       Format: 'YYYY-MM-DD HH:mm' or "YYYY-MM-DD HH:mm"
+       Example: '2017-09-15 17:25'
+
+   Date Only
+   **********
+   This date will be taken as midnight UTC of that day
+
+   .. code::
+
+       Format: YYYY-MM-DD
+       Example: 2017-09-15
+
+   Epoch seconds
+   **************
+   .. code::
+
+       Example: 1412195400
+
+--time-started [datetime]
+
+An optional filter to return audit events whose creation time in the
+database is greater than and equal to the date-time specified, in the
+format defined by RFC3339.
+
+   The following datetime formats are supported:
+
+
+UTC with microseconds
+---------------------
+
+   Format: YYYY-MM-DDTHH:mm:ss.ssssssTZD
+   Example: 2017-09-15T20:30:00.123456Z
+
+   UTC with milliseconds
+   ***********************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ss.sssTZD
+       Example: 2017-09-15T20:30:00.123Z
+
+   UTC without milliseconds
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T20:30:00Z
+
+   UTC with minute precision
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T20:30Z
+
+
+Timezone with microseconds
+--------------------------
+
+   Format: YYYY-MM-DDTHH:mm:ssTZD
+   Example: 2017-09-15T12:30:00.456789-08:00, 2017-09-15T12:30:00.456789-0800
+
+   Timezone with milliseconds
+   ***************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00.456-08:00, 2017-09-15T12:30:00.456-0800
+
+   Timezone without milliseconds
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00-08:00, 2017-09-15T12:30:00-0800
+
+   Timezone with minute precision
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T12:30-08:00, 2017-09-15T12:30-0800
+
+   Short date and time
+   ********************
+   The timezone for this date and time will be taken as UTC (Needs to be surrounded by single or double quotes)
+
+   .. code::
+
+       Format: 'YYYY-MM-DD HH:mm' or "YYYY-MM-DD HH:mm"
+       Example: '2017-09-15 17:25'
+
+   Date Only
+   **********
+   This date will be taken as midnight UTC of that day
+
+   .. code::
+
+       Format: YYYY-MM-DD
+       Example: 2017-09-15
+
+   Epoch seconds
+   **************
+   .. code::
+
+       Example: 1412195400
+
 
 Global Parameters
 =================

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/database-security-config/list.txt

@@ -155,6 +155,11 @@ 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/database-table-access-entry-collection/list-database-table-access-entries.txt

@@ -94,7 +94,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=(accessType eq ‘SELECT’) and (grantee eq ‘ADMIN’)
+**Example:** query=(accessType eq “SELECT”) and (grantee eq “ADMIN”)
 
 --sort-by [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/database-view-access-entry-collection/list-database-view-access-entries.txt

@@ -94,7 +94,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=(accessType eq ‘SELECT’) and (grantee eq ‘ADMIN’)
+**Example:** query=(accessType eq “SELECT”) and (grantee eq “ADMIN”)
 
 --sort-by [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/masking-column/list.txt

@@ -153,7 +153,7 @@ default order for other fields is ascending.
 
 Accepted values are:
 
-   dataType, objectName, schemaName, timeCreated
+   columnName, dataType, objectName, schemaName, timeCreated
 
 --sort-order [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/masking-policy/list-masking-analytics.txt

@@ -79,7 +79,7 @@ Attribute by which the masking analytics data should be grouped.
 
 Accepted values are:
 
-   policyId, targetId
+   policyId, sensitiveTypeId, targetId, targetIdAndPolicyId
 
 --limit [integer]
 
@@ -104,6 +104,33 @@ Pagination.
 When fetching results, the number of results to fetch per call. Only
 valid when used with "--all" or "--limit", and ignored otherwise.
 
+--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:
+
+   timeLastMasked
+
+--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/masking-policy-referential-relation-summary/list-masking-policy-referential-relations.txt

@@ -117,7 +117,7 @@ The field to sort by. You can specify only one sorting parameter
 
 Accepted values are:
 
-   columnName, relationType, schemaName, tableName
+   objectName, relationType, schemaName
 
 --sort-order [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/on-prem-connector/list.txt

@@ -88,6 +88,15 @@ 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
 
+--lifecycle-state [text]
+
+A filter to return only on-premises connector resources that match the
+specified lifecycle state.
+
+Accepted values are:
+
+   ACTIVE, CREATING, DELETED, DELETING, FAILED, INACTIVE, NEEDS_ATTENTION, UPDATING
+
 --limit [integer]
 
 For list pagination. The maximum number of items to return per page in
@@ -99,15 +108,6 @@ List Pagination.
 A filter to return only the on-premises connector that matches the
 specified id.
 
---on-prem-connector-lifecycle-state [text]
-
-A filter to return only on-premises connector resources that match the
-specified lifecycle state.
-
-Accepted values are:
-
-   ACTIVE, CREATING, DELETED, DELETING, FAILED, INACTIVE, NEEDS_ATTENTION, UPDATING
-
 --page [text]
 
 For list pagination. The page token representing the page at which to

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/peer-target-database/create-peer-target-database-database-cloud-service-details.txt

@@ -38,10 +38,6 @@ Accepted values are:
 
    CLOUD_AT_CUSTOMER, NON_ORACLE_CLOUD, ON_PREMISES, ORACLE_CLOUD
 
---database-details-service-name [text]
-
-The database service name.
-
 --target-database-id [text]
 
 The OCID of the Data Safe target database.
@@ -59,6 +55,15 @@ Safe.
 
 The port number of the database listener.
 
+--database-details-pluggable-database-id [text]
+
+The OCID of the pluggable database registered as a target database in
+Data Safe.
+
+--database-details-service-name [text]
+
+The database service name.
+
 --database-details-vm-cluster-id [text]
 
 The OCID of the VM cluster in which the database is running.
@@ -179,8 +184,7 @@ 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/create.html#cmdoption-compartment-id
        export database_details_infrastructure_type=<substitute-value-of-database_details_infrastructure_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/data-safe/peer-target-database/create-peer-target-database-database-cloud-service-details.html#cmdoption-database-details-infrastructure-type
-       export database_details_service_name=<substitute-value-of-database_details_service_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/data-safe/peer-target-database/create-peer-target-database-database-cloud-service-details.html#cmdoption-database-details-service-name
 
        target_database_id=$(oci data-safe target-database create --compartment-id $compartment_id --database-details file://database-details.json --query data.id --raw-output)
 
-       oci data-safe peer-target-database create-peer-target-database-database-cloud-service-details --database-details-infrastructure-type $database_details_infrastructure_type --database-details-service-name $database_details_service_name --target-database-id $target_database_id
+       oci data-safe peer-target-database create-peer-target-database-database-cloud-service-details --database-details-infrastructure-type $database_details_infrastructure_type --target-database-id $target_database_id

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/peer-target-database/update-peer-target-database-database-cloud-service-details.txt

@@ -38,10 +38,6 @@ Accepted values are:
 
    CLOUD_AT_CUSTOMER, NON_ORACLE_CLOUD, ON_PREMISES, ORACLE_CLOUD
 
---database-details-service-name [text]
-
-The database service name.
-
 --peer-target-database-id [integer]
 
 The unique id of the peer target database.
@@ -63,6 +59,15 @@ Safe.
 
 The port number of the database listener.
 
+--database-details-pluggable-database-id [text]
+
+The OCID of the pluggable database registered as a target database in
+Data Safe.
+
+--database-details-service-name [text]
+
+The database service name.
+
 --database-details-vm-cluster-id [text]
 
 The OCID of the VM cluster in which the database is running.
@@ -182,10 +187,9 @@ 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/create.html#cmdoption-compartment-id
        export database_details_infrastructure_type=<substitute-value-of-database_details_infrastructure_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/data-safe/peer-target-database/update-peer-target-database-database-cloud-service-details.html#cmdoption-database-details-infrastructure-type
-       export database_details_service_name=<substitute-value-of-database_details_service_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/data-safe/peer-target-database/update-peer-target-database-database-cloud-service-details.html#cmdoption-database-details-service-name
 
        target_database_id=$(oci data-safe target-database create --compartment-id $compartment_id --database-details file://database-details.json --query data.id --raw-output)
 
        peer_target_database_id=$(oci data-safe peer-target-database create --database-details file://database-details.json --target-database-id $target_database_id --query data.id --raw-output)
 
-       oci data-safe peer-target-database update-peer-target-database-database-cloud-service-details --database-details-infrastructure-type $database_details_infrastructure_type --database-details-service-name $database_details_service_name --peer-target-database-id $peer_target_database_id --target-database-id $target_database_id
+       oci data-safe peer-target-database update-peer-target-database-database-cloud-service-details --database-details-infrastructure-type $database_details_infrastructure_type --peer-target-database-id $peer_target_database_id --target-database-id $target_database_id

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/report-definition/generate-report.txt

@@ -106,8 +106,19 @@ 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=(dateGenerated ge ‘2021-12-18T01-00-26’) and
-(ilmTarget eq ‘dscs-target’)
+**Example:** query=(auditEventTime ge “2021-06-04T01:00:26.000Z”) and
+(eventName eq “LOGON”)
+
+--target-group-ids [complex type]
+
+Array of target group OCIDs. 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.
 
 --target-ids [complex type]
 

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/report-summary/list-reports.txt

@@ -62,6 +62,15 @@ Default is false. When set to true, the hierarchy of compartments is
 traversed and all compartments and subcompartments in the tenancy are
 returned. Depends on the ‘accessLevel’ setting.
 
+--data-source [text]
+
+Specifies the name of a resource that provides data for the report.
+For example  alerts, events.
+
+Accepted values are:
+
+   ALERTS, ALLOWED_SQL, EVENTS, SECURITY_ASSESSMENT, VIOLATIONS
+
 --display-name [text]
 
 The name of the report definition to query.

oci_cli/help_text_producer/data_files/text/cmdref/data-safe/security-assessment/apply-security-assessment-template.txt

@@ -0,0 +1,134 @@
+"apply-security-assessment-template"
+************************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Apply the checks from the template to the specified security
+assessment.The security assessment provided in the path needs to be of
+type ‘LATEST’.
+
+
+Usage
+=====
+
+   oci data-safe security-assessment apply-security-assessment-template [OPTIONS]
+
+
+Required Parameters
+===================
+
+--security-assessment-id [text]
+
+The OCID of the security assessment.
+
+
+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.
+
+--template-assessment-id [text]
+
+The OCID of the template type security assessment containing the check
+details.
+
+--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 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/security-assessment/create.html#cmdoption-compartment-id
+
+       security_assessment_id=$(oci data-safe security-assessment create --compartment-id $compartment_id --query data.id --raw-output)
+
+       oci data-safe security-assessment apply-security-assessment-template --security-assessment-id $security_assessment_id