stemaMSFT
commented
1 year ago As @grayzu has previously mentioned, an additional parameter around the "scenario" that can be passed into modules would be tremendously helpful in simplifying especially the more complex ones (i.e. AKS). For example, having a "basic" non-production parameterized iteration, and the ability to change that single property to update all the properties in the module to something more production ready. We could thus expose more properties in the complex examples, but encourage and give guidance to have people start with the simpler modules then transition to the more complex as they feel comfortable.
Module Scenario
This issue is inspired by this Aks module's issue.
Our legacy modules are becoming more and more complex.
A good example for scenario-focued modules could be: CloudPosse has created the following different modules that provision Aws subnet:
WDYT?
Proposed module name
multiple modules
Link to existing example module
No response
Expected resources
No response
Module inputs
Module outputs
No response
Other information
No response