Optimize AppSync resolver deployment by skipping unchanged VTL templates #14534
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.
optimize AppSync resolver deployment by skipping unchanged VTL templates
Performance improvement for AppSync APIs with many resolvers where only
a subset have changed. This optimization can significantly reduce deployment
time by avoiding re-uploading identical VTL mapping templates to S3.
The optimization process:
This change is backward compatible and opt-in via the --skip-unchanged-resolvers flag.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.