Allow users to enable the default registry #504
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
N/A
Description of changes:
While not officially supported, it is possible to alias an ECR registry with DNS (eg ecr.example.io).
This change adds support for the
AWS_ECR_USE_DEFAULT_REGISTRY
environment variable which, when set to a non-empty value, will force this tool to use the default registry when authenticating.I am not married to this implementation; if the maintainers have a better idea for allowing users to use this tool with non-AWS-style registry names I'm happy to try to implement!
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.