Initiates the process of asset metadata synchronization with the related asset source.
The OCID of the asset source.
Provide input to this command as a JSON document from a file using the file://path-to/file syntax.
--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
The maximum time to wait for the work request to reach the state defined by
--wait-for-state. Defaults to 1200 seconds.
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 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, WAITING
--wait-interval-seconds to see whether the work request has reached the state defined by
--wait-for-state. Defaults to 30 seconds.
oci --help for help on global parameters.
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/cloud-bridge/inventory/inventory/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/cloud-bridge/inventory/inventory/create.html#cmdoption-display-name export assets_compartment_id=<substitute-value-of-assets_compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/cloud-bridge/discovery/asset-source/create.html#cmdoption-assets-compartment-id export type=<substitute-value-of-type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/cloud-bridge/discovery/asset-source/create.html#cmdoption-type environment_id=$(oci cloud-bridge ocb-agent-svc environment create --compartment-id $compartment_id --query data.id --raw-output) inventory_id=$(oci cloud-bridge inventory inventory create --compartment-id $compartment_id --display-name $display_name --query data.id --raw-output) asset_source_id=$(oci cloud-bridge discovery asset-source create --assets-compartment-id $assets_compartment_id --compartment-id $compartment_id --environment-id $environment_id --inventory-id $inventory_id --type $type --query data.id --raw-output) oci cloud-bridge discovery asset-source refresh --asset-source-id $asset_source_id