add restrict-resources-by-module-source.sentinel #268
Merged
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.
This adds a new restrict-resources-by-modules-source.sentinel poilcy that restricts resources of specific types to only be created in modules with sources in a given list. It used the tfconfig/v2 import and a new function, get_module_source(), that I added to the tfconfig-functions.sentinel module. There is a new MD file to describe that new function.
It also fixes an error in the recently added restrict-s3-bucket-policies.sentinel policy, replacing an occurrence of
break
withcontinue
.It also changes some comments in the MD file for tfconfig-functions.find_descendant_modules() to refer to module labels instead of names and fixes a broken link in that file.
And it makes a mior typographical change in aws-functions.sentinel to change
num_segments -1
tonum_segments-1
.