aws codeartifact copy-package-versions
Copies package versions from one repository to another repository in the same domain. You must specify versions or versionRevisions. You cannot specify both
Options
Name | Description |
---|---|
--domain <string> | The name of the domain that contains the source and destination repositories |
--domain-owner <string> | The 12-digit account number of the AWS account that owns the domain. It does not include dashes or spaces |
--source-repository <string> | The name of the repository that contains the package versions to copy |
--destination-repository <string> | The name of the repository into which package versions are copied |
--format <string> | The format of the package that is copied. The valid package types are: npm: A Node Package Manager (npm) package. pypi: A Python Package Index (PyPI) package. maven: A Maven package that contains compiled code in a distributable format, such as a JAR file |
--namespace <string> | The namespace of the package. 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. A Python package does not contain a corresponding component, so Python packages do not have a namespace |
--package <string> | The name of the package that is copied |
--versions <list> | The versions of the package to copy. You must specify versions or versionRevisions. You cannot specify both |
--version-revisions <map> | A list of key-value pairs. The keys are package versions and the values are package version revisions. A CopyPackageVersion operation succeeds if the specified versions in the source repository match the specified package version revision. You must specify versions or versionRevisions. You cannot specify both |
--allow-overwrite | Set to true to overwrite a package version that already exists in the destination repository. If set to false and the package version already exists in the destination repository, the package version is returned in the failedVersions field of the response with an ALREADY_EXISTS error code |
--no-allow-overwrite | Set to true to overwrite a package version that already exists in the destination repository. If set to false and the package version already exists in the destination repository, the package version is returned in the failedVersions field of the response with an ALREADY_EXISTS error code |
--include-from-upstream | Set to true to copy packages from repositories that are upstream from the source repository to the destination repository. The default setting is false. For more information, see Working with upstream repositories |
--no-include-from-upstream | Set to true to copy packages from repositories that are upstream from the source repository to the destination repository. The default setting is false. For more information, see Working with upstream repositories |
--cli-input-json <string> | Performs service operation based on the JSON string provided. The JSON string follows the format provided by ``--generate-cli-skeleton``. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally |
--generate-cli-skeleton <string> | Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value ``input``, prints a sample input JSON that can be used as an argument for ``--cli-input-json``. If provided with the value ``output``, it validates the command inputs and returns a sample output JSON for that command |