fix: Skip image-repository validation of ECR images (#2934) #3015
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.
Which issue(s) does this change fix?
Issue #2934
Why is this change necessary?
image_repository_validation
for Docker-packaged lambda functions with valid ECR locations (Issue Skip Docker Lambda image builds when ImageUri is a valid ECR location #2934, introduced in PR fix: Skip build of Docker image if ImageUri is a valid ECR URL (#2934) #2935);--guided
guided context prompts.DockerContext
resource metadata prior to skipping the image build.How does it address the issue?
get_template_function_resource_ids
,get_template_artifacts_format
), use theSamFunctionProvider
to do so (evaluating template parameters values, so the template must go through the IntrinsicResolver).What side effects does this change have?
get_template_function_resource_ids
,get_template_artifacts_format
are obsolete (not yet deleted from the repo);Checklist
make pr
passesmake update-reproducible-reqs
if dependencies were changedBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.