@codiac.io/codiac-cli 1.2.216 → 1.2.219

package/dist/ops/docker-registry-api-client/entities/blob-sum.js

@@ -1,13 +1,13 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.Blob = void 0;
-class Blob {
-    /**
-     * @param blobSum Digest
-     */
-    constructor(blobSum) {
-        this.blobSum = blobSum;
-    }
-}
-exports.Blob = Blob;
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.Blob = void 0;
+class Blob {
+    /**
+     * @param blobSum Digest
+     */
+    constructor(blobSum) {
+        this.blobSum = blobSum;
+    }
+}
+exports.Blob = Blob;
 //# sourceMappingURL=blob-sum.js.map

package/dist/ops/docker-registry-api-client/entities/docker-access-actions-enum.d.ts

@@ -1,5 +1,5 @@
-/** The names of the permissions granted in (or requested for) a token's Access Control List (ACL). */
-export declare enum DockerActionPermissionsEnum {
-    pull = "pull",
-    push = "push"
-}
+/** The names of the permissions granted in (or requested for) a token's Access Control List (ACL). */
+export declare enum DockerActionPermissionsEnum {
+    pull = "pull",
+    push = "push"
+}

package/dist/ops/docker-registry-api-client/entities/docker-access-actions-enum.js

@@ -1,10 +1,10 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.DockerActionPermissionsEnum = void 0;
-/** The names of the permissions granted in (or requested for) a token's Access Control List (ACL). */
-var DockerActionPermissionsEnum;
-(function (DockerActionPermissionsEnum) {
-    DockerActionPermissionsEnum["pull"] = "pull";
-    DockerActionPermissionsEnum["push"] = "push";
-})(DockerActionPermissionsEnum = exports.DockerActionPermissionsEnum || (exports.DockerActionPermissionsEnum = {}));
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.DockerActionPermissionsEnum = void 0;
+/** The names of the permissions granted in (or requested for) a token's Access Control List (ACL). */
+var DockerActionPermissionsEnum;
+(function (DockerActionPermissionsEnum) {
+    DockerActionPermissionsEnum["pull"] = "pull";
+    DockerActionPermissionsEnum["push"] = "push";
+})(DockerActionPermissionsEnum = exports.DockerActionPermissionsEnum || (exports.DockerActionPermissionsEnum = {}));
 //# sourceMappingURL=docker-access-actions-enum.js.map

package/dist/ops/docker-registry-api-client/entities/docker-auth-token-criteria.d.ts

@@ -1,30 +1,30 @@
-export declare class DockerAuthTokenCriteria {
-    service: string;
-    scope: string;
-    offline_token?: boolean | undefined;
-    client_id?: string | undefined;
-    /**
-     *
-     * @param service The name of the service which hosts the resource.  eg:  "registry.docker.io"
-     * @param scope TL;DR: Colon-delimited string in format:  "[scopeLevel]:[scopeName]:[actions]".  eg: "?scope=repository:letmeaskmydog/toyhauler-base:pull,push".
-     *        The resource in question, formatted as one of the space-delimited entries from the scope parameters
-     *        from the WWW-Authenticate header returned in an http 401 response.
-     *        This query parameter should be specified multiple times if there is more than one scope entry
-     *        from the WWW-Authenticate header.
-     *        The scope field may be empty to request a refresh token without providing any resource permissions to the returned bearer token.
-     *
-     * @param offline_token Whether to return a refresh token along with the bearer token.
-     *         A refresh token is capable of getting additional bearer tokens for the same subject with different scopes.
-     *         The refresh token does not have an expiration and should be considered completely opaque to the client.
-     * @param client_id String identifying the client. This client_id does not need to be registered with the authorization server
-     *         but should be set to a meaningful value in order to allow auditing keys created by unregistered clients.
-     *         Accepted syntax is defined in [RFC6749 Appendix A.1](https://tools.ietf.org/html/rfc6749#appendix-A.1).
-     *
-     * @see https://docs.docker.com/registry/spec/auth/token/#how-to-authenticate How to Authenticate
-     * @see https://docs.docker.com/registry/spec/auth/token/#requesting-a-token Requesting a Token
-     * @see https://docs.docker.com/registry/spec/auth/jwt/ Token Authentication Implementation
-     * @see https://tools.ietf.org/html/rfc6750#section-3 Section 3 of RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage
-     * @see https://tools.ietf.org/html/rfc6749#appendix-A.1 RFC6749 Appendix A.1
-     */
-    constructor(service: string, scope: string, offline_token?: boolean | undefined, client_id?: string | undefined);
-}
+export declare class DockerAuthTokenCriteria {
+    service: string;
+    scope: string;
+    offline_token?: boolean | undefined;
+    client_id?: string | undefined;
+    /**
+     *
+     * @param service The name of the service which hosts the resource.  eg:  "registry.docker.io"
+     * @param scope TL;DR: Colon-delimited string in format:  "[scopeLevel]:[scopeName]:[actions]".  eg: "?scope=repository:letmeaskmydog/toyhauler-base:pull,push".
+     *        The resource in question, formatted as one of the space-delimited entries from the scope parameters
+     *        from the WWW-Authenticate header returned in an http 401 response.
+     *        This query parameter should be specified multiple times if there is more than one scope entry
+     *        from the WWW-Authenticate header.
+     *        The scope field may be empty to request a refresh token without providing any resource permissions to the returned bearer token.
+     *
+     * @param offline_token Whether to return a refresh token along with the bearer token.
+     *         A refresh token is capable of getting additional bearer tokens for the same subject with different scopes.
+     *         The refresh token does not have an expiration and should be considered completely opaque to the client.
+     * @param client_id String identifying the client. This client_id does not need to be registered with the authorization server
+     *         but should be set to a meaningful value in order to allow auditing keys created by unregistered clients.
+     *         Accepted syntax is defined in [RFC6749 Appendix A.1](https://tools.ietf.org/html/rfc6749#appendix-A.1).
+     *
+     * @see https://docs.docker.com/registry/spec/auth/token/#how-to-authenticate How to Authenticate
+     * @see https://docs.docker.com/registry/spec/auth/token/#requesting-a-token Requesting a Token
+     * @see https://docs.docker.com/registry/spec/auth/jwt/ Token Authentication Implementation
+     * @see https://tools.ietf.org/html/rfc6750#section-3 Section 3 of RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage
+     * @see https://tools.ietf.org/html/rfc6749#appendix-A.1 RFC6749 Appendix A.1
+     */
+    constructor(service: string, scope: string, offline_token?: boolean | undefined, client_id?: string | undefined);
+}

package/dist/ops/docker-registry-api-client/entities/docker-auth-token-criteria.js

@@ -1,36 +1,36 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.DockerAuthTokenCriteria = void 0;
-class DockerAuthTokenCriteria {
-    /**
-     *
-     * @param service The name of the service which hosts the resource.  eg:  "registry.docker.io"
-     * @param scope TL;DR: Colon-delimited string in format:  "[scopeLevel]:[scopeName]:[actions]".  eg: "?scope=repository:letmeaskmydog/toyhauler-base:pull,push".
-     *        The resource in question, formatted as one of the space-delimited entries from the scope parameters
-     *        from the WWW-Authenticate header returned in an http 401 response.
-     *        This query parameter should be specified multiple times if there is more than one scope entry
-     *        from the WWW-Authenticate header.
-     *        The scope field may be empty to request a refresh token without providing any resource permissions to the returned bearer token.
-     *
-     * @param offline_token Whether to return a refresh token along with the bearer token.
-     *         A refresh token is capable of getting additional bearer tokens for the same subject with different scopes.
-     *         The refresh token does not have an expiration and should be considered completely opaque to the client.
-     * @param client_id String identifying the client. This client_id does not need to be registered with the authorization server
-     *         but should be set to a meaningful value in order to allow auditing keys created by unregistered clients.
-     *         Accepted syntax is defined in [RFC6749 Appendix A.1](https://tools.ietf.org/html/rfc6749#appendix-A.1).
-     *
-     * @see https://docs.docker.com/registry/spec/auth/token/#how-to-authenticate How to Authenticate
-     * @see https://docs.docker.com/registry/spec/auth/token/#requesting-a-token Requesting a Token
-     * @see https://docs.docker.com/registry/spec/auth/jwt/ Token Authentication Implementation
-     * @see https://tools.ietf.org/html/rfc6750#section-3 Section 3 of RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage
-     * @see https://tools.ietf.org/html/rfc6749#appendix-A.1 RFC6749 Appendix A.1
-     */
-    constructor(service, scope, offline_token, client_id) {
-        this.service = service;
-        this.scope = scope;
-        this.offline_token = offline_token;
-        this.client_id = client_id;
-    }
-}
-exports.DockerAuthTokenCriteria = DockerAuthTokenCriteria;
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.DockerAuthTokenCriteria = void 0;
+class DockerAuthTokenCriteria {
+    /**
+     *
+     * @param service The name of the service which hosts the resource.  eg:  "registry.docker.io"
+     * @param scope TL;DR: Colon-delimited string in format:  "[scopeLevel]:[scopeName]:[actions]".  eg: "?scope=repository:letmeaskmydog/toyhauler-base:pull,push".
+     *        The resource in question, formatted as one of the space-delimited entries from the scope parameters
+     *        from the WWW-Authenticate header returned in an http 401 response.
+     *        This query parameter should be specified multiple times if there is more than one scope entry
+     *        from the WWW-Authenticate header.
+     *        The scope field may be empty to request a refresh token without providing any resource permissions to the returned bearer token.
+     *
+     * @param offline_token Whether to return a refresh token along with the bearer token.
+     *         A refresh token is capable of getting additional bearer tokens for the same subject with different scopes.
+     *         The refresh token does not have an expiration and should be considered completely opaque to the client.
+     * @param client_id String identifying the client. This client_id does not need to be registered with the authorization server
+     *         but should be set to a meaningful value in order to allow auditing keys created by unregistered clients.
+     *         Accepted syntax is defined in [RFC6749 Appendix A.1](https://tools.ietf.org/html/rfc6749#appendix-A.1).
+     *
+     * @see https://docs.docker.com/registry/spec/auth/token/#how-to-authenticate How to Authenticate
+     * @see https://docs.docker.com/registry/spec/auth/token/#requesting-a-token Requesting a Token
+     * @see https://docs.docker.com/registry/spec/auth/jwt/ Token Authentication Implementation
+     * @see https://tools.ietf.org/html/rfc6750#section-3 Section 3 of RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage
+     * @see https://tools.ietf.org/html/rfc6749#appendix-A.1 RFC6749 Appendix A.1
+     */
+    constructor(service, scope, offline_token, client_id) {
+        this.service = service;
+        this.scope = scope;
+        this.offline_token = offline_token;
+        this.client_id = client_id;
+    }
+}
+exports.DockerAuthTokenCriteria = DockerAuthTokenCriteria;
 //# sourceMappingURL=docker-auth-token-criteria.js.map

package/dist/ops/docker-registry-api-client/entities/i-docker-error-response.d.ts

@@ -1,55 +1,55 @@
-export interface IDockerErrorResponse {
-    errors: IDockerError[];
-}
-export interface IDockerError {
-    code: DockerErrorCodesEnum;
-    message: string;
-    detail: any;
-}
-export declare enum DockerErrorCodesEnum {
-    /** MESSAGE: blob unknown to registry
-     * This error may be returned when a blob is unknown to the registry in a specified repository. This can be returned with a standard get or if a manifest references an unknown layer during upload. */
-    BLOB_UNKNOWN = "BLOB_UNKNOWN",
-    /** MESSAGE: blob upload invalid
-     * The blob upload encountered an error and can no longer proceed. */
-    BLOB_UPLOAD_INVALID = "BLOB_UPLOAD_INVALID",
-    /** MESSAGE: blob upload unknown to registry
-     * If a blob upload has been cancelled or was never started, this error code may be returned. */
-    BLOB_UPLOAD_UNKNOWN = "BLOB_UPLOAD_UNKNOWN",
-    /** MESSAGE: provided digest did not match uploaded content
-     * When a blob is uploaded, the registry will check that the content matches the digest provided by the client. The error may include a detail structure with the key “digest”, including the invalid digest string. This error may also be returned when a manifest includes an invalid layer digest. */
-    DIGEST_INVALID = "DIGEST_INVALID",
-    /** MESSAGE: blob unknown to registry
-     * This error may be returned when a manifest blob is unknown to the registry. */
-    MANIFEST_BLOB_UNKNOWN = "MANIFEST_BLOB_UNKNOWN",
-    /** MESSAGE: manifest invalid
-     * During upload, manifests undergo several checks ensuring validity. If those checks fail, this error may be returned, unless a more specific error is included. The detail will contain information the failed validation. */
-    MANIFEST_INVALID = "MANIFEST_INVALID",
-    /** MESSAGE: manifest unknown
-     * This error is returned when the manifest, identified by name and tag is unknown to the repository. */
-    MANIFEST_UNKNOWN = "MANIFEST_UNKNOWN",
-    /** MESSAGE: manifest failed signature verification
-     * During manifest upload, if the manifest fails signature verification, this error will be returned. */
-    MANIFEST_UNVERIFIED = "MANIFEST_UNVERIFIED",
-    /** MESSAGE: invalid repository name
-     * Invalid repository name encountered either during manifest validation or any API operation. */
-    NAME_INVALID = "NAME_INVALID",
-    /** MESSAGE: repository name not known to registry
-     * This is returned if the name used during an operation is unknown to the registry. */
-    NAME_UNKNOWN = "NAME_UNKNOWN",
-    /** MESSAGE: provided length did not match content length
-     * When a layer is uploaded, the provided size will be checked against the uploaded content. If they do not match, this error will be returned. */
-    SIZE_INVALID = "SIZE_INVALID",
-    /** MESSAGE: manifest tag did not match URI
-     * During a manifest upload, if the tag in the manifest does not match the uri tag, this error will be returned. */
-    TAG_INVALID = "TAG_INVALID",
-    /** MESSAGE: authentication required
-     * The access controller was unable to authenticate the client. Often this will be accompanied by a Www-Authenticate HTTP response header indicating how to authenticate. */
-    UNAUTHORIZED = "UNAUTHORIZED",
-    /** MESSAGE: requested access to the resource is denied
-     * The access controller denied access for the operation on a resource. */
-    DENIED = "DENIED",
-    /** MESSAGE: The operation is unsupported.
-     * The operation was unsupported due to a missing implementation or invalid set of parameters. */
-    UNSUPPORTED = "UNSUPPORTED"
-}
+export interface IDockerErrorResponse {
+    errors: IDockerError[];
+}
+export interface IDockerError {
+    code: DockerErrorCodesEnum;
+    message: string;
+    detail: any;
+}
+export declare enum DockerErrorCodesEnum {
+    /** MESSAGE: blob unknown to registry
+     * This error may be returned when a blob is unknown to the registry in a specified repository. This can be returned with a standard get or if a manifest references an unknown layer during upload. */
+    BLOB_UNKNOWN = "BLOB_UNKNOWN",
+    /** MESSAGE: blob upload invalid
+     * The blob upload encountered an error and can no longer proceed. */
+    BLOB_UPLOAD_INVALID = "BLOB_UPLOAD_INVALID",
+    /** MESSAGE: blob upload unknown to registry
+     * If a blob upload has been cancelled or was never started, this error code may be returned. */
+    BLOB_UPLOAD_UNKNOWN = "BLOB_UPLOAD_UNKNOWN",
+    /** MESSAGE: provided digest did not match uploaded content
+     * When a blob is uploaded, the registry will check that the content matches the digest provided by the client. The error may include a detail structure with the key “digest”, including the invalid digest string. This error may also be returned when a manifest includes an invalid layer digest. */
+    DIGEST_INVALID = "DIGEST_INVALID",
+    /** MESSAGE: blob unknown to registry
+     * This error may be returned when a manifest blob is unknown to the registry. */
+    MANIFEST_BLOB_UNKNOWN = "MANIFEST_BLOB_UNKNOWN",
+    /** MESSAGE: manifest invalid
+     * During upload, manifests undergo several checks ensuring validity. If those checks fail, this error may be returned, unless a more specific error is included. The detail will contain information the failed validation. */
+    MANIFEST_INVALID = "MANIFEST_INVALID",
+    /** MESSAGE: manifest unknown
+     * This error is returned when the manifest, identified by name and tag is unknown to the repository. */
+    MANIFEST_UNKNOWN = "MANIFEST_UNKNOWN",
+    /** MESSAGE: manifest failed signature verification
+     * During manifest upload, if the manifest fails signature verification, this error will be returned. */
+    MANIFEST_UNVERIFIED = "MANIFEST_UNVERIFIED",
+    /** MESSAGE: invalid repository name
+     * Invalid repository name encountered either during manifest validation or any API operation. */
+    NAME_INVALID = "NAME_INVALID",
+    /** MESSAGE: repository name not known to registry
+     * This is returned if the name used during an operation is unknown to the registry. */
+    NAME_UNKNOWN = "NAME_UNKNOWN",
+    /** MESSAGE: provided length did not match content length
+     * When a layer is uploaded, the provided size will be checked against the uploaded content. If they do not match, this error will be returned. */
+    SIZE_INVALID = "SIZE_INVALID",
+    /** MESSAGE: manifest tag did not match URI
+     * During a manifest upload, if the tag in the manifest does not match the uri tag, this error will be returned. */
+    TAG_INVALID = "TAG_INVALID",
+    /** MESSAGE: authentication required
+     * The access controller was unable to authenticate the client. Often this will be accompanied by a Www-Authenticate HTTP response header indicating how to authenticate. */
+    UNAUTHORIZED = "UNAUTHORIZED",
+    /** MESSAGE: requested access to the resource is denied
+     * The access controller denied access for the operation on a resource. */
+    DENIED = "DENIED",
+    /** MESSAGE: The operation is unsupported.
+     * The operation was unsupported due to a missing implementation or invalid set of parameters. */
+    UNSUPPORTED = "UNSUPPORTED"
+}

package/dist/ops/docker-registry-api-client/entities/i-docker-error-response.js

@@ -1,52 +1,52 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.DockerErrorCodesEnum = void 0;
-var DockerErrorCodesEnum;
-(function (DockerErrorCodesEnum) {
-    /** MESSAGE: blob unknown to registry
-     * This error may be returned when a blob is unknown to the registry in a specified repository. This can be returned with a standard get or if a manifest references an unknown layer during upload. */
-    DockerErrorCodesEnum["BLOB_UNKNOWN"] = "BLOB_UNKNOWN";
-    /** MESSAGE: blob upload invalid
-     * The blob upload encountered an error and can no longer proceed. */
-    DockerErrorCodesEnum["BLOB_UPLOAD_INVALID"] = "BLOB_UPLOAD_INVALID";
-    /** MESSAGE: blob upload unknown to registry
-     * If a blob upload has been cancelled or was never started, this error code may be returned. */
-    DockerErrorCodesEnum["BLOB_UPLOAD_UNKNOWN"] = "BLOB_UPLOAD_UNKNOWN";
-    /** MESSAGE: provided digest did not match uploaded content
-     * When a blob is uploaded, the registry will check that the content matches the digest provided by the client. The error may include a detail structure with the key “digest”, including the invalid digest string. This error may also be returned when a manifest includes an invalid layer digest. */
-    DockerErrorCodesEnum["DIGEST_INVALID"] = "DIGEST_INVALID";
-    /** MESSAGE: blob unknown to registry
-     * This error may be returned when a manifest blob is unknown to the registry. */
-    DockerErrorCodesEnum["MANIFEST_BLOB_UNKNOWN"] = "MANIFEST_BLOB_UNKNOWN";
-    /** MESSAGE: manifest invalid
-     * During upload, manifests undergo several checks ensuring validity. If those checks fail, this error may be returned, unless a more specific error is included. The detail will contain information the failed validation. */
-    DockerErrorCodesEnum["MANIFEST_INVALID"] = "MANIFEST_INVALID";
-    /** MESSAGE: manifest unknown
-     * This error is returned when the manifest, identified by name and tag is unknown to the repository. */
-    DockerErrorCodesEnum["MANIFEST_UNKNOWN"] = "MANIFEST_UNKNOWN";
-    /** MESSAGE: manifest failed signature verification
-     * During manifest upload, if the manifest fails signature verification, this error will be returned. */
-    DockerErrorCodesEnum["MANIFEST_UNVERIFIED"] = "MANIFEST_UNVERIFIED";
-    /** MESSAGE: invalid repository name
-     * Invalid repository name encountered either during manifest validation or any API operation. */
-    DockerErrorCodesEnum["NAME_INVALID"] = "NAME_INVALID";
-    /** MESSAGE: repository name not known to registry
-     * This is returned if the name used during an operation is unknown to the registry. */
-    DockerErrorCodesEnum["NAME_UNKNOWN"] = "NAME_UNKNOWN";
-    /** MESSAGE: provided length did not match content length
-     * When a layer is uploaded, the provided size will be checked against the uploaded content. If they do not match, this error will be returned. */
-    DockerErrorCodesEnum["SIZE_INVALID"] = "SIZE_INVALID";
-    /** MESSAGE: manifest tag did not match URI
-     * During a manifest upload, if the tag in the manifest does not match the uri tag, this error will be returned. */
-    DockerErrorCodesEnum["TAG_INVALID"] = "TAG_INVALID";
-    /** MESSAGE: authentication required
-     * The access controller was unable to authenticate the client. Often this will be accompanied by a Www-Authenticate HTTP response header indicating how to authenticate. */
-    DockerErrorCodesEnum["UNAUTHORIZED"] = "UNAUTHORIZED";
-    /** MESSAGE: requested access to the resource is denied
-     * The access controller denied access for the operation on a resource. */
-    DockerErrorCodesEnum["DENIED"] = "DENIED";
-    /** MESSAGE: The operation is unsupported.
-     * The operation was unsupported due to a missing implementation or invalid set of parameters. */
-    DockerErrorCodesEnum["UNSUPPORTED"] = "UNSUPPORTED";
-})(DockerErrorCodesEnum = exports.DockerErrorCodesEnum || (exports.DockerErrorCodesEnum = {}));
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.DockerErrorCodesEnum = void 0;
+var DockerErrorCodesEnum;
+(function (DockerErrorCodesEnum) {
+    /** MESSAGE: blob unknown to registry
+     * This error may be returned when a blob is unknown to the registry in a specified repository. This can be returned with a standard get or if a manifest references an unknown layer during upload. */
+    DockerErrorCodesEnum["BLOB_UNKNOWN"] = "BLOB_UNKNOWN";
+    /** MESSAGE: blob upload invalid
+     * The blob upload encountered an error and can no longer proceed. */
+    DockerErrorCodesEnum["BLOB_UPLOAD_INVALID"] = "BLOB_UPLOAD_INVALID";
+    /** MESSAGE: blob upload unknown to registry
+     * If a blob upload has been cancelled or was never started, this error code may be returned. */
+    DockerErrorCodesEnum["BLOB_UPLOAD_UNKNOWN"] = "BLOB_UPLOAD_UNKNOWN";
+    /** MESSAGE: provided digest did not match uploaded content
+     * When a blob is uploaded, the registry will check that the content matches the digest provided by the client. The error may include a detail structure with the key “digest”, including the invalid digest string. This error may also be returned when a manifest includes an invalid layer digest. */
+    DockerErrorCodesEnum["DIGEST_INVALID"] = "DIGEST_INVALID";
+    /** MESSAGE: blob unknown to registry
+     * This error may be returned when a manifest blob is unknown to the registry. */
+    DockerErrorCodesEnum["MANIFEST_BLOB_UNKNOWN"] = "MANIFEST_BLOB_UNKNOWN";
+    /** MESSAGE: manifest invalid
+     * During upload, manifests undergo several checks ensuring validity. If those checks fail, this error may be returned, unless a more specific error is included. The detail will contain information the failed validation. */
+    DockerErrorCodesEnum["MANIFEST_INVALID"] = "MANIFEST_INVALID";
+    /** MESSAGE: manifest unknown
+     * This error is returned when the manifest, identified by name and tag is unknown to the repository. */
+    DockerErrorCodesEnum["MANIFEST_UNKNOWN"] = "MANIFEST_UNKNOWN";
+    /** MESSAGE: manifest failed signature verification
+     * During manifest upload, if the manifest fails signature verification, this error will be returned. */
+    DockerErrorCodesEnum["MANIFEST_UNVERIFIED"] = "MANIFEST_UNVERIFIED";
+    /** MESSAGE: invalid repository name
+     * Invalid repository name encountered either during manifest validation or any API operation. */
+    DockerErrorCodesEnum["NAME_INVALID"] = "NAME_INVALID";
+    /** MESSAGE: repository name not known to registry
+     * This is returned if the name used during an operation is unknown to the registry. */
+    DockerErrorCodesEnum["NAME_UNKNOWN"] = "NAME_UNKNOWN";
+    /** MESSAGE: provided length did not match content length
+     * When a layer is uploaded, the provided size will be checked against the uploaded content. If they do not match, this error will be returned. */
+    DockerErrorCodesEnum["SIZE_INVALID"] = "SIZE_INVALID";
+    /** MESSAGE: manifest tag did not match URI
+     * During a manifest upload, if the tag in the manifest does not match the uri tag, this error will be returned. */
+    DockerErrorCodesEnum["TAG_INVALID"] = "TAG_INVALID";
+    /** MESSAGE: authentication required
+     * The access controller was unable to authenticate the client. Often this will be accompanied by a Www-Authenticate HTTP response header indicating how to authenticate. */
+    DockerErrorCodesEnum["UNAUTHORIZED"] = "UNAUTHORIZED";
+    /** MESSAGE: requested access to the resource is denied
+     * The access controller denied access for the operation on a resource. */
+    DockerErrorCodesEnum["DENIED"] = "DENIED";
+    /** MESSAGE: The operation is unsupported.
+     * The operation was unsupported due to a missing implementation or invalid set of parameters. */
+    DockerErrorCodesEnum["UNSUPPORTED"] = "UNSUPPORTED";
+})(DockerErrorCodesEnum = exports.DockerErrorCodesEnum || (exports.DockerErrorCodesEnum = {}));
 //# sourceMappingURL=i-docker-error-response.js.map

package/dist/ops/docker-registry-api-client/entities/i-docker-list-response.d.ts

@@ -1,7 +1,7 @@
-/** Response envelope for lists of entities. */
-export interface IDockerListResponse<T> {
-    count: number;
-    next?: string;
-    previous?: string;
-    results: T[];
-}
+/** Response envelope for lists of entities. */
+export interface IDockerListResponse<T> {
+    count: number;
+    next?: string;
+    previous?: string;
+    results: T[];
+}

package/dist/ops/docker-registry-api-client/entities/i-docker-list-response.js

@@ -1,3 +1,3 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
 //# sourceMappingURL=i-docker-list-response.js.map

package/dist/ops/docker-registry-api-client/entities/image-repository.d.ts

@@ -1,31 +1,31 @@
-export declare class ImageRepository {
-    /** eg: "pivotalrabbitmq/rabbitmq-autocluster", */
-    repo_name: string;
-    /** eg: "RabbitMQ with the rabbitmq-autocluster plugin.", */
-    short_description: string;
-    /** eg: 3, */
-    star_count: number;
-    /** eg: 582815, */
-    pull_count: number;
-    /** eg: "", */
-    repo_owner: string;
-    /** eg: false, */
-    is_automated: boolean;
-    /** eg: false */
-    is_official: boolean;
-    constructor(
-    /** eg: "pivotalrabbitmq/rabbitmq-autocluster", */
-    repo_name: string, 
-    /** eg: "RabbitMQ with the rabbitmq-autocluster plugin.", */
-    short_description: string, 
-    /** eg: 3, */
-    star_count: number, 
-    /** eg: 582815, */
-    pull_count: number, 
-    /** eg: "", */
-    repo_owner: string, 
-    /** eg: false, */
-    is_automated: boolean, 
-    /** eg: false */
-    is_official: boolean);
-}
+export declare class ImageRepository {
+    /** eg: "pivotalrabbitmq/rabbitmq-autocluster", */
+    repo_name: string;
+    /** eg: "RabbitMQ with the rabbitmq-autocluster plugin.", */
+    short_description: string;
+    /** eg: 3, */
+    star_count: number;
+    /** eg: 582815, */
+    pull_count: number;
+    /** eg: "", */
+    repo_owner: string;
+    /** eg: false, */
+    is_automated: boolean;
+    /** eg: false */
+    is_official: boolean;
+    constructor(
+    /** eg: "pivotalrabbitmq/rabbitmq-autocluster", */
+    repo_name: string, 
+    /** eg: "RabbitMQ with the rabbitmq-autocluster plugin.", */
+    short_description: string, 
+    /** eg: 3, */
+    star_count: number, 
+    /** eg: 582815, */
+    pull_count: number, 
+    /** eg: "", */
+    repo_owner: string, 
+    /** eg: false, */
+    is_automated: boolean, 
+    /** eg: false */
+    is_official: boolean);
+}

package/dist/ops/docker-registry-api-client/entities/image-repository.js

@@ -1,30 +1,30 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.ImageRepository = void 0;
-class ImageRepository {
-    constructor(
-    /** eg: "pivotalrabbitmq/rabbitmq-autocluster", */
-    repo_name, 
-    /** eg: "RabbitMQ with the rabbitmq-autocluster plugin.", */
-    short_description, 
-    /** eg: 3, */
-    star_count, 
-    /** eg: 582815, */
-    pull_count, 
-    /** eg: "", */
-    repo_owner, 
-    /** eg: false, */
-    is_automated, 
-    /** eg: false */
-    is_official) {
-        this.repo_name = repo_name;
-        this.short_description = short_description;
-        this.star_count = star_count;
-        this.pull_count = pull_count;
-        this.repo_owner = repo_owner;
-        this.is_automated = is_automated;
-        this.is_official = is_official;
-    }
-}
-exports.ImageRepository = ImageRepository;
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ImageRepository = void 0;
+class ImageRepository {
+    constructor(
+    /** eg: "pivotalrabbitmq/rabbitmq-autocluster", */
+    repo_name, 
+    /** eg: "RabbitMQ with the rabbitmq-autocluster plugin.", */
+    short_description, 
+    /** eg: 3, */
+    star_count, 
+    /** eg: 582815, */
+    pull_count, 
+    /** eg: "", */
+    repo_owner, 
+    /** eg: false, */
+    is_automated, 
+    /** eg: false */
+    is_official) {
+        this.repo_name = repo_name;
+        this.short_description = short_description;
+        this.star_count = star_count;
+        this.pull_count = pull_count;
+        this.repo_owner = repo_owner;
+        this.is_automated = is_automated;
+        this.is_official = is_official;
+    }
+}
+exports.ImageRepository = ImageRepository;
 //# sourceMappingURL=image-repository.js.map

package/dist/ops/docker-registry-api-client/entities/image-tag-criteria.d.ts

@@ -1,8 +1,8 @@
-/**
- *
- */
-export declare class ImageTagCriteria {
-    name: string;
-    /** @param name Name of the image repository. */
-    constructor(name: string);
-}
+/**
+ *
+ */
+export declare class ImageTagCriteria {
+    name: string;
+    /** @param name Name of the image repository. */
+    constructor(name: string);
+}

package/dist/ops/docker-registry-api-client/entities/image-tag-criteria.js

@@ -1,14 +1,14 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.ImageTagCriteria = void 0;
-/**
- *
- */
-class ImageTagCriteria {
-    /** @param name Name of the image repository. */
-    constructor(name) {
-        this.name = name;
-    }
-}
-exports.ImageTagCriteria = ImageTagCriteria;
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ImageTagCriteria = void 0;
+/**
+ *
+ */
+class ImageTagCriteria {
+    /** @param name Name of the image repository. */
+    constructor(name) {
+        this.name = name;
+    }
+}
+exports.ImageTagCriteria = ImageTagCriteria;
 //# sourceMappingURL=image-tag-criteria.js.map

package/dist/ops/docker-registry-api-client/entities/image-tag-list.d.ts

@@ -1,7 +1,7 @@
-/** An object listiong tags for a given image repository.
- */
-export declare class ImageTagList {
-    name: string;
-    tags: string[];
-    constructor(name: string, tags: string[]);
-}
+/** An object listiong tags for a given image repository.
+ */
+export declare class ImageTagList {
+    name: string;
+    tags: string[];
+    constructor(name: string, tags: string[]);
+}