Provide the details about the destination datastore in JSON structure either in-line or via a local file, file://path-to/data-sync-destination-json-file.
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
Short description of the Task Definition
If provided, it sets the data transfer rate limit for this task. Allowed values are 50M, 100M, 250M, 500M, 1G, 2G, or 5G. Default to unlimited if not provided.
Provide the details about how the task execution is scheduled in JSON structure either in-line or via a local file, file://path-to/schedule-json-file.
Provide the details about the source datastore in JSON structure either in-line or via a local file, file://path-to/data-sync-source-json-file.
oci --help for help on global parameters.
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.
export id=<substitute-value-of-id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/rover/device/data-sync/task-definition/update.html#cmdoption-id oci rover device data-sync task-definition update --id $id