DMZ Tagging: Support multiple tags, move to panther_config #1019
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
jof
force-pushed
the
jof/public/dmz-multiple-tags
branch
3 times, most recently
from
4f3eb8e to
ff915d0
Compare
jof
force-pushed
the
jof/public/dmz-multiple-tags
branch
from
ff915d0 to
b8f37bd
Compare
egibs
previously approved these changes
Dec 12, 2023
egibs
approved these changes
Dec 12, 2023
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.
Background
Support multiple possible DMZ key/value pairs to denote intentionally-exposed resources.
This also moves the tag settings into the
panther_configsystem to enable easy overrides in private forks of this repo.Changes
panther_config