Displayed name of diagnostic bundle
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
Wait for a diagnostic bundle to reach a specific state (seconds)
Rover Node Name
Use Basic Authentication for Diagnostic Requets - Retrieved from Serial Console
Wait for a diagnostic bundle to reach a
specific 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 FAILED would
return on whichever lifecycle state is
Accepted values are:
ACCEPTED, COMPLETED, FAILED, IN_PROGRESS
Frequency to poll the state of a diagnostic bundle (seconds)
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.
oci rover device diagnostics bundle create