Spec Template for Folder/Contents
Add a new type of spec template that points to a folder rather a specific file.
Add a new type of spec template that points to a folder rather a specific file. The “folder spec template” would be added to a layout (terraform) along with several standard file-spec templates (pointing to terraform files). The “folder spec template” would bring in all the sub-contents into the layout’s working folder, along with all the terraform files associated with the standard file based spec templates. This would allow terraform code to reference the files from the folder in cases like:
- user_data
- API JSON specifications
- Container definitions
- database configurations
This is very useful especially when deployments occur from a single catalog item, but you want to give the provisioning user “t-shirt sizes” style flexibility to choose from 1 or more types of user_data, or different sized container specs, or a higher performing database…etc … without requiring the user to fill out 10’s upon 10’s of form fields.
This is all about customer experience, self-service, and adoption, while still keeping governance, compliance, policy, and controls in mind by using standardized, approved, and version controlled configuration as code.
Example/Use case(s):
(Replace with mock workflow/example/diagram when applicable)