Cherry-pick #23204 to 7.11: simplify regex for org & custom prefix in aws/cloudtrail #23207
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.
Cherry-pick of PR #23204 to 7.11 branch. Original message:
What does this PR do?
changes regex to only match on /CloudTrail/, /CloudTrail-Digest/ and
/CloudTrail-Insight/. This removes the prefix which is variable based
on custom prefix and organization.
Why is it important?
cloudtrail will work if you have custom prefix or organization. And
you will still be able to skip Digest or Insight logs if necessary.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Need to test in AWS with custom prefix or organization. Did test
regex against known cloudtrail filename patterns.
Related issues