View Source aws_marketplace_catalog (aws v0.7.15)
Catalog API actions allow you to manage your entities through list, describe, and update capabilities.
An entity can be a product or an offer on AWS Marketplace.
You can automate your entity update process by integrating the AWS Marketplace Catalog API with your AWS Marketplace product build or deployment pipelines. You can also create your own applications on top of the Catalog API to manage your products on AWS Marketplace.Link to this section Summary
Functions
Used to cancel an open change request.
Returns the list of change sets owned by the account being used to make the call.
Allows you to request changes for your entities.
Link to this section Functions
Used to cancel an open change request.
Must be sent before the status of the request changes toAPPLYING
, the final stage of completing your change request. You can describe a change during the 60-day request history retention period for API calls.
describe_change_set(Client, Catalog, ChangeSetId, QueryMap, HeadersMap)
View Sourcedescribe_change_set(Client, Catalog, ChangeSetId, QueryMap, HeadersMap, Options0)
View Sourcedescribe_entity(Client, Catalog, EntityId, QueryMap, HeadersMap, Options0)
View SourceReturns the list of change sets owned by the account being used to make the call.
You can filter this list by providing any combination of entityId
, ChangeSetName
, and status. If you provide more than one filter, the API operation applies a logical AND between the filters.
Allows you to request changes for your entities.
Within a single ChangeSet
, you can't start the same change type against the same entity multiple times. Additionally, when a ChangeSet
is running, all the entities targeted by the different changes are locked until the change set has completed (either succeeded, cancelled, or failed). If you try to start a change set containing a change against an entity that is already locked, you will receive a ResourceInUseException
error.
For example, you can't start the ChangeSet
described in the example later in this topic because it contains two changes to run the same change type (AddRevisions
) against the same entity (entity-id@1
).