feat: Add ability for controlling whether or not to create a policy #163
Conversation
examples/iam-policy/main.tf
Outdated
| source = "../../modules/iam-policy" | ||
| create_policy = false | ||
|
|
||
| name = "example_optional" |
There was a problem hiding this comment.
There are default values already specified for all variables in the module, so you can remove everything starting from line 61 (like here).
There was a problem hiding this comment.
Ok, I've removed "path" and "description".
Thank you for your time!
There was a problem hiding this comment.
Please remove everything and leave just source and create_policy = false with empty line in between.
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Add ability for controlling whether or not to create a policy
Motivation and Context
In certain scenarios can be useful to decide which specific policy should be created or not. Let's imagine that we create a module from this module for creating a set of policies that might change depending on the account you are targeting. This change allows you to do that.
Breaking Changes
There is no breaking change as the module still behaving the same by default.
How Has This Been Tested?
examples/*projects