Add cron failure monitoring SNS topic to IAM policy for Lambda #25268
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
sgress454
requested review from
rfairburn,
ksatter,
lukeheath,
edwardsb and
georgekarrv
as code owners
rfairburn
approved these changes
Jan 8, 2025
rfairburn
pushed a commit
that referenced
this pull request
Jan 16, 2025
@rfairburn at your convenience, after tagging #25268 plz approve and merge.
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.
for #25267
This was missed in the TF config for the cron-monitoring Lambda updates, leading to a failure when trying to publish to the
#help-p2topic.