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

CountsSummary

import type { CountsSummary } from "https://aws-api.deno.dev/v0.4/services/proton.ts?docs=full";

Summary counts of each Proton resource type.

interface CountsSummary {
components?: ResourceCountsSummary | null;
environments?: ResourceCountsSummary | null;
environmentTemplates?: ResourceCountsSummary | null;
pipelines?: ResourceCountsSummary | null;
serviceInstances?: ResourceCountsSummary | null;
services?: ResourceCountsSummary | null;
serviceTemplates?: ResourceCountsSummary | null;
}

§Properties

§
components?: ResourceCountsSummary | null
[src]

The total number of components in the Amazon Web Services account.

The semantics of the components field are different from the semantics of results for other infrastructure-provisioning resources. That's because at this time components don't have associated templates, therefore they don't have the concept of staleness. The components object will only contain total and failed members.

§
environments?: ResourceCountsSummary | null
[src]

The staleness counts for Proton environments in the Amazon Web Services account. The environments object will only contain total members.

§
environmentTemplates?: ResourceCountsSummary | null
[src]

The total number of environment templates in the Amazon Web Services account.

§
pipelines?: ResourceCountsSummary | null
[src]

The staleness counts for Proton pipelines in the Amazon Web Services account.

§
serviceInstances?: ResourceCountsSummary | null
[src]

The staleness counts for Proton service instances in the Amazon Web Services account.

§
services?: ResourceCountsSummary | null
[src]

The staleness counts for Proton services in the Amazon Web Services account.

§
serviceTemplates?: ResourceCountsSummary | null
[src]

The total number of service templates in the Amazon Web Services account. The serviceTemplates object will only contain total members.