update

Description

Updates a specific data asset with default connection.

Usage

oci data-integration data-asset update [OPTIONS]

Required Parameters

--data-asset-key [text]

Data asset key.

--key [text]

Generated key that can be used in API calls to identify data asset.

--model-type [text]

The type of the data asset.

Accepted values are:

ORACLE_ADWC_DATA_ASSET, ORACLE_ATP_DATA_ASSET, ORACLE_DATA_ASSET, ORACLE_OBJECT_STORAGE_DATA_ASSET
--object-version [integer]

The version of the object that is used to track changes in the object instance.

--workspace-id [text]

DIS workspace id

Optional Parameters

--asset-properties [complex type]

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

--credential-file-content [text]

The credential file content from a wallet for the data asset.

--default-connection [text]

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]

Detailed description for the object.

--driver-class [text]

The driver class for the data asset.

--external-key [text]

The external key for the object

--force

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

--host [text]

The host details for the data asset.

--identifier [text]

Value can only contain upper case letters, underscore and numbers. It should begin with upper case letter or underscore. The value can be edited by the user.

--if-match [text]

Update and Delete operations should accept an optional If-Match header, in which clients can send a previously-received ETag. When If-Match is provided and its value does not exactly match the ETag of the resource on the server, the request should fail with HTTP response status code 412

--model-version [text]

The model version of an object.

--name [text]

Free form text without any restriction on permitted characters. Name can have letters, numbers, and special characters. The value can be edited by the user and it is restricted to 1000 characters

--namespace [text]

Free form text without any restriction on permitted characters. Name can have letters, numbers, and special characters. The value can be edited by the user and it is restricted to 1000 characters

--object-status [integer]

The status of an object that can be set to value 1 for shallow references across objects, other values reserved.

--port [text]

The port details for the data asset.

--registry-metadata [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.

--service-name [text]

The service name for the data asset.

--sid [text]

sid

--tenancy-id [text]

The OCI tenancy OCID.

--url [text]

url