Include publisher ARN's when interrogating the publisher #972
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
martincostello
approved these changes
Feb 4, 2022
Codecov Report
@@ Coverage Diff @@
## main #972 +/- ##
==========================================
- Coverage 84.27% 84.02% -0.26%
==========================================
Files 131 131
Lines 3206 3211 +5
==========================================
- Hits 2702 2698 -4
- Misses 504 513 +9
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
We encountered a situation in which we wanted to know what topic name is generated from a naming convention, and found that interrogation doesn't emit ARN's or generated topic names. This PR adds them so you can now see what message type is published to an ARN.