CLI Commands

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, changing it as needed and then passing it back in through the file:// syntax.

The type of attachment the OAC instance is using.

Accepted values are:

MANAGED

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, changing it as needed and then passing it back in through the file:// syntax.

The OCID of the ResourceAnalyticsInstance.

The OCID of the TenancyAttachment.

Regions to be included with data collection. The region ID, For example, us-ashburn-1. At least one region is required. 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, changing it as needed and then passing it back in through the file:// syntax.

Free-form tags for this resource. Each tag is a 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, changing it as needed and then passing it back in through the file:// syntax.

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 prepopulated and match the command option names (converted to camelCase format, for example, compartment-id becomes 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 many 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 are used.

For examples on usage of this option, see, using CLI with advanced JSON options

Perform deletion without prompting for confirmation.

Perform update without prompting for confirmation.

A filter to return only resources that match the specific lifecycle state. The state value is case-insensitive.

Accepted values are:

ACTIVE, CREATING, DELETED, DELETING, FAILED, UPDATING

List of Network Security Group OCID's. 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, changing it as needed and then passing it back in through the file:// syntax.

The OCID of the ResourceAnalyticsInstance.

The OCID of a ResourceAnalyticsInstance.

The field to sort by. You can provide only one sort order. Default order for TIME_CREATED is descending. Default order for DISPLAY_NAME is ascending.

Accepted values are:

DISPLAY_NAME, TIME_CREATED

The field to sort by. Only one sort order may be provided. Default order for timeAccepted is descending.

Accepted values are:

timeAccepted

The sort order to use, either ascending (ASC) or descending (DESC).

Accepted values are:

ASC, DESC

A filter to return only the resources that match the specific lifecycle state.

Accepted values are:

ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, NEEDS_ATTENTION, SUCCEEDED, WAITING

This operation asynchronously creates, changes 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. Several 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, NEEDS_ATTENTION, SUCCEEDED, WAITING