Fix lambda provisioned concurrency setup #7045
Merged
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #7045 +/- ##
==========================================
- Coverage 88.5% 88.49% -0.02%
==========================================
Files 230 230
Lines 8473 8473
==========================================
- Hits 7499 7498 -1
- Misses 974 975 +1
Continue to review full report at Codecov.
|
|
The issue still seems to be there with the new version (1.59.3). Every deployment is creating additional provisioned concurrenies. I have set versionFunctions: false. |
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.
When testing locally it now, when it's available, I've realized it was not setup properly, and that it should be setup on
AWS::Lambda::Versionresource.Having that patch in, I've successfully deployed new lambdas with provisioned concurrency setup.
However I observed
Internal errorCF stack udpate crashes when trying to update already deployed lambdas with that config (This looks as AWS issue, which I discuss with them over email)