create-data-source-atp

Description

Creates a new DataAsset.

Usage

oci anomaly-detection data-asset create-data-source-atp [OPTIONS]

Required Parameters

--compartment-id, -c [text]

The OCID for the data asset’s compartment.

--project-id [text]

The OCID of the project to associate with the data asset.

Optional Parameters

--atp-password-secret-id [text]

atp db password Secret Id

--atp-user-name [text]

atp db user name

--cwallet-file-secret-id [text]

OCID of the secret containing the containers certificates of ATP wallet

--database-name [text]

atp database name

--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.

--description [text]

A short description of the Ai data asset

--display-name [text]

A user-friendly display name for the resource. It does not have to be unique and can be modified. Avoid entering confidential information.

--ewallet-file-secret-id [text]

OCID of the secret containing the PDB’S certificates of ATP wallet

--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/Content/API/SDKDocs/cliusing.htm#AdvancedJSONOptions

--key-store-file-secret-id [text]

OCID of the secret containing Keystore.jks file of the ATP wallet

--max-wait-seconds [integer]

The maximum time to wait for the resource to reach the lifecycle state defined by --wait-for-state. Defaults to 1200 seconds.

--ojdbc-file-secret-id [text]

OCID of the secret that contains jdbc properties file of ATP wallet

--private-endpoint-id [text]

OCID of Private Endpoint.

--table-name [text]

atp database table name

--tnsnames-file-secret-id [text]

OCID of the secret that contains the tnsnames file of ATP wallet

--truststore-file-secret-id [text]

OCID of the secret containing truststore.jks file of the ATP wallet

--wait-for-state [text]

This operation creates, modifies or deletes a resource that has a defined lifecycle state. Specify this option to perform the action and then wait until the resource reaches a given lifecycle state. Multiple states can be specified, returning on the first state. For example, --wait-for-state SUCCEEDED --wait-for-state FAILED would return on whichever lifecycle state is reached first. If timeout is reached, a return code of 2 is returned. For any other error, a return code of 1 is returned.

Accepted values are:

ACTIVE, DELETED
--wait-interval-seconds [integer]

Check every --wait-interval-seconds to see whether the resource has reached the lifecycle state defined by --wait-for-state. Defaults to 30 seconds.

--wallet-password-secret-id [text]

wallet password Secret ID in String format

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/anomaly-detection/project/create.html#cmdoption-compartment-id

    project_id=$(oci anomaly-detection project create --compartment-id $compartment_id --query data.id --raw-output)

    oci anomaly-detection data-asset create-data-source-atp --compartment-id $compartment_id --project-id $project_id