Moves a Lockbox resource from one compartment identifier to another. When provided, If-Match is checked against ETag values of the resource.


oci oma lockbox change-compartment [OPTIONS]

Required Parameters

--compartment-id, -c [text]

The unique identifier (OCID) of the compartment where the resource is located.

--lockbox-id [text]

unique Lockbox identifier

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:

--if-match [text]

For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.

Example using required parameter

Copy and paste the following example into a JSON file, replacing the example parameters with your own.

    oci oma lockbox create --generate-param-json-input context-attributes > context-attributes.json

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 compartment_id=<substitute-value-of-compartment_id> #
    export lockbox_partner=<substitute-value-of-lockbox_partner> #
    export partner_compartment_id=<substitute-value-of-partner_compartment_id> #
    export resource_id=<substitute-value-of-resource_id> #

    lockbox_id=$(oci oma lockbox create --compartment-id $compartment_id --context-attributes file://context-attributes.json --lockbox-partner $lockbox_partner --partner-compartment-id $partner_compartment_id --resource-id $resource_id --query --raw-output)

    oci oma lockbox change-compartment --compartment-id $compartment_id --lockbox-id $lockbox_id