The AutoCloud Consumer Flow allows users to generate Terraform code using the Blueprints created by Terraform producers. In order to use the consumer flow, a user will select the blueprint they want to create code for by navigating to AutoCloud's IaC Catalog page, which looks like this:
After determining the blueprint they want to use, the consumer can read instructions on how to use the blueprint by clicking the three dots in the top right of the blueprint's card and selecting instructions
Clicking the generate button on the blueprint's card will initiate the process of generating the Terraform code using the Blueprint.
The consumer will then be navigated to a multi-step form wizard where they can enter any of the values required to configure how the Terraform code for that blueprint will be generated. The actual form field inputs are dependent on the individual blueprint and how it was configured during the Producer Flow. Like most forms, required inputs are specified by a red asterisk next to the form input's label.
After filling out the form, the consumer will click theNEXTbutton and move to the next phase of the blueprint. This phase will run a complete policy scan against the Terraform code that will be generated to ensure it follows the compliance requirements of the organization.
After reviewing the policy scan and ensuring there are no compliance issues, the consumer can click NEXT to navigate to the projected cost phase of the blueprint. This phase will provide an estimate of what the cloud resources resulting from the generated Terraform code will cost if they are deployed.
The consumer can now click NEXT one more time to navigate to the REVIEW step of the blueprint. Here, the consumer can see the values they have entered from the form as well as the compliance and cost results. If everything looks correct, the consumer can click the SUBMIT button. Once clicked, the blueprint will generate the requested Terraform code and open a pull request with this generated code in the configured repo. The blueprint will also, optionally, create a JIRA ticket with a link to the opened pull request and details on the pull request such as what blueprint it was created with and who the consumer who used the blueprint is.