Fix deployment failure when missing lambda version #24
Conversation
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
Eli-Meitner
requested review from
raanan245,
evgenygigi,
srinivas-toluna,
waseemkh88 and
morozov-toluna
waseemkh88
approved these changes
Sep 19, 2023
srinivas-toluna
approved these changes
Sep 19, 2023
evgenygigi
approved these changes
Sep 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In current state the versions are calculated as published version and published version-1, this sometimes causes the build to fail if versions are not in running sequence,
THE FIX: get published version for latest, and current "Alias" version as current version