Skip to content

Commit

Permalink
docs(aws-ecr-assets): Update link for cdk-ecr-deployment repo (#15407)
Browse files Browse the repository at this point in the history
Link for cdk-ecr-deployment was https://github.com/wchaws/cdk-ecr-deployment, but is now https://github.com/cdklabs/cdk-ecr-deployment. Just updated this links.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
  • Loading branch information
antonioortegajr authored Jul 7, 2021
1 parent c37c7f9 commit ef12609
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions packages/@aws-cdk/aws-ecr-assets/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,10 +77,10 @@ The mechanics of where these images are published and how are intentionally kept
does not support customizations such as specifying the ECR repository name or tags.

If you are looking for a way to _publish_ image assets to an ECR repository in your control, you should consider using
[wchaws/cdk-ecr-deployment], which is able to replicate an image asset from the CDK-controlled ECR repository to a repository of
[cdklabs/cdk-ecr-deployment], which is able to replicate an image asset from the CDK-controlled ECR repository to a repository of
your choice.

Here an example from the [wchaws/cdk-ecr-deployment] project:
Here an example from the [cdklabs/cdk-ecr-deployment] project:

```ts
import * as ecrdeploy from 'cdk-ecr-deployment';
Expand All @@ -99,7 +99,7 @@ new ecrdeploy.ECRDeployment(this, 'DeployDockerImage', {
You are welcome to +1 [this GitHub issue](https://github.com/aws/aws-cdk/issues/12597) if you would like to see
native support for this use-case in the AWS CDK.

[wchaws/cdk-ecr-deployment]: https://github.com/wchaws/cdk-ecr-deployment
[cdklabs/cdk-ecr-deployment]: https://github.com/cdklabs/cdk-ecr-deployment

## Pull Permissions

Expand Down

0 comments on commit ef12609

Please sign in to comment.