Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

MarketplaceCatalog

import { MarketplaceCatalog } from "https://aws-api.deno.dev/v0.3/services/marketplacecatalog.ts?docs=full";
class MarketplaceCatalog {
constructor(apiFactory: client.ApiFactory);
async cancelChangeSet(params: CancelChangeSetRequest, opts?: client.RequestOptions): Promise<CancelChangeSetResponse>;
async describeChangeSet(params: DescribeChangeSetRequest, opts?: client.RequestOptions): Promise<DescribeChangeSetResponse>;
async describeEntity(params: DescribeEntityRequest, opts?: client.RequestOptions): Promise<DescribeEntityResponse>;
async listChangeSets(params: ListChangeSetsRequest, opts?: client.RequestOptions): Promise<ListChangeSetsResponse>;
async listEntities(params: ListEntitiesRequest, opts?: client.RequestOptions): Promise<ListEntitiesResponse>;
async startChangeSet(params: StartChangeSetRequest, opts?: client.RequestOptions): Promise<StartChangeSetResponse>;
 
static ApiMetadata: client.ApiMetadata;
}

§Constructors

§
new MarketplaceCatalog(apiFactory: client.ApiFactory)
[src]

§Methods

§

Used to cancel an open change request. Must be sent before the status of the request changes to APPLYING, the final stage of completing your change request. You can describe a change during the 60-day request history retention period for API calls.

§

Provides information about a given change set.

§

Returns the metadata and content of the entity.

§

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

You can describe a change during the 60-day request history retention period for API calls.

§

Provides the list of entities of a given type.

§

This operation allows you to request changes for your entities. Within a single ChangeSet, you cannot 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 ChangeSet has completed (either succeeded, cancelled, or failed). If you try to start a ChangeSet containing a change against an entity that is already locked, you will receive a ResourceInUseException.

For example, you cannot start the ChangeSet described in the example later in this topic, because it contains two changes to execute the same change type (AddRevisions) against the same entity (entity-id@1).

For more information about working with change sets, see Working with change sets.

§Static Properties