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

PutPackageOriginConfigurationRequest

import type { PutPackageOriginConfigurationRequest } from "https://aws-api.deno.dev/v0.4/services/codeartifact.ts?docs=full";
interface PutPackageOriginConfigurationRequest {
domain: string;
domainOwner?: string | null;
format: PackageFormat;
namespace?: string | null;
package: string;
repository: string;
}

§Properties

§
domain: string
[src]

The name of the domain that contains the repository that contains the package.

§
domainOwner?: string | null
[src]

The 12-digit account number of the Amazon Web Services account that owns the domain. It does not include dashes or spaces.

§

A format that specifies the type of the package to be updated.

§
namespace?: string | null
[src]

The namespace of the package to be updated. The package component that specifies its namespace depends on its type. For example:

  • The namespace of a Maven package is its groupId.
  • The namespace of an npm package is its scope.
  • Python and NuGet packages do not contain a corresponding component, packages of those formats do not have a namespace.
§
package: string
[src]

The name of the package to be updated.

§
repository: string
[src]

The name of the repository that contains the package.

§

A PackageOriginRestrictions object that contains information about the upstream and publish package origin restrictions. The upstream restriction determines if new package versions can be ingested or retained from external connections or upstream repositories. The publish restriction determines if new package versions can be published directly to the repository.

You must include both the desired upstream and publish restrictions.