Removes a previously accepted terms of use agreement from the list of agreements that Marketplace checks before initiating a deployment. Listings in Marketplace that require acceptance of the specified terms of use can no longer be deployed, but existing deployments aren’t affected.


oci marketplace accepted-agreement delete [OPTIONS]

Required Parameters

--accepted-agreement-id [text]

The unique identifier for the accepted terms of use agreement.

Optional Parameters


Perform deletion without prompting for confirmation.

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

--signature [text]

Previously, the signature generated for the listing package terms of use agreement, but now deprecated and ignored.

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 agreement_id=<substitute-value-of-agreement_id> #
    export compartment_id=<substitute-value-of-compartment_id> #
    export listing_id=<substitute-value-of-listing_id> #
    export package_version=<substitute-value-of-package_version> #
    export signature=<substitute-value-of-signature> #

    accepted_agreement_id=$(oci marketplace accepted-agreement create --agreement-id $agreement_id --compartment-id $compartment_id --listing-id $listing_id --package-version $package_version --signature $signature --query --raw-output)

    oci marketplace accepted-agreement delete --accepted-agreement-id $accepted_agreement_id