feat: ElasticLoadBalancingV2 TargetGroups, provisioned concurrency support #26
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.
Proposed changes
@flagsmith
scope, an NPM publish job triggered by GitHub releases, and bumped the package version.Types of changes
What types of changes does your code introduce to the plugin?
Checklist
Further comments
The logic to determine whether a given function has provisioned concurrency/SnapStart configured is simplifed greatly on behalf of the framework's internal code that sets a
targetAlias
property to the function configuration in any of those cases. This is not documented anywhere, but that code has been stable across both the major versions. For greater compatibility with other plugins that may rely on this, we set and/or update the functions'targetAlias
es with proper names and logical IDs.