feat: Add policy path to fargate_fluentbit #442
Merged
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
donovanmuller
force-pushed
the
fargate-fluentbit-policypath
branch
from
bcf3b05 to
f4de1e6
Compare
donovanmuller
changed the title
bryantbiggs
approved these changes
Feb 18, 2025
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.
What does this PR do?
Adds
pathargument toaws_iam_policy.fargate_fluentbit.Motivation
I want to be able to provide a custom path for the
fargate_fluentbitpolicy to adhere to security constraints within some organisations.More
pre-commit run -awith this PRFor Moderators
Additional Notes
Similar to #96