feat: [DEV-536] publish version and update alias after function deploy#202
Merged
Conversation
After uploading the zip, wait for the update to settle, publish an immutable version, and point the function's single alias to it. Errors if more than one alias is found. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
ArielSantos01
changed the title
…loys to prod Full service deploy via deploy:prod remains available. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
After deploying a Lambda function's code, the deploy:func commands now wait for the update to settle, publish an immutable version, and update the function's alias to point to it.
Task Context
What is the current behavior?
deploy:func:dev/prod/feature uploads the zip via update-function-code and stops there. The alias (if any) keeps pointing to the previous version.
What is the new behavior?
After uploading the zip, the command:
Additional Context