Gets a secret bundle that matches either the specified stage, secretVersionName, or versionNumber parameter. If none of these parameters are provided, the bundle for the secret version marked as CURRENT will be returned.


oci secrets secret-bundle get [OPTIONS]

Required Parameters

--secret-id [text]

The OCID of the secret.

Optional Parameters

--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:

--secret-version-name [text]

The name of the secret. (This might be referred to as the name of the secret version. Names are unique across the different versions of a secret.)

--stage [text]

The rotation state of the secret version.

Accepted values are:

--version-number [integer]

The version number of the secret.

Example using required parameter

Copy the following CLI commands into a file named Run the command by typing “bash” 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 secret_id=<substitute-value-of-secret_id> #

    oci secrets secret-bundle get --secret-id $secret_id