feat: update event invoke config with alias#149
Open
ojongerius wants to merge 1 commit into
Open
Conversation
Author
|
One thing to mentioned might be, I'm updating instead of adding the EventInvokeConfig. When adding an When generating these snippets of CF template: and AWS actually would only create an Ev config for for the unqualified function: But not the alias: |
Author
|
@davidgf have a moment to review? |
Author
|
@davidgf ping! :) |
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
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
This change updates the EventInvokeConfig to point to the alias created. This means that Destinations, MaximumEventAgeInSeconds and MaximumRetryAttempts were previously only applied to the unqualified ARN instead of the alias.
Types of changes
What types of changes does your code introduce to the plugin?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.