Blueprint YAML Overview

Stack Automation blueprints are reusable components designed to model a required deployment from the infrastructure to the application. Blueprint designers utilize Stack Automation's VSCode plugin or the Stack Automation's self-service UI to build a YAML based imperative blueprints that aimed to fulfill business requirements in a self-service manner for their end-users.

Note

Blueprints are written in YAML files that reside in a /blueprints folder within a Github, Gitlab or BitBucket repository (the folder name is case-sensitive and must be "blueprints"). The /blueprints folder must be defined as the blueprint repository in the space's Settings > Repositories page. Blueprints file type must be ".yaml" and not ".yml".

For enhanced asset discovery and organization, see Stack Automation Assets Markers.

Common example will be a platform team or a DevOps team building Dev, Test and staging deployments for their development, QA and product teams. With Stack Automation, the DevOps team can focus on design, best practices, and security for the deployment, while their end users are being self-served from the Stack Automation UI or API based on governance and policies without having the 'keys-to-the-cloud'.

Grain Categories

Stack Automation provides different types of grains per use case:

• Core Blueprint Structure: Blueprint YAML first
• Configuration Management: Ansible
• CI/CD and GitOps: ArgoCD
• Nested Blueprints: Blueprint Grain
• Infrastructure as Code: CDK, CloudFormation, OpenTofu, Terraform, Terragrunt
• Platform Integration: CloudShell
• Container Orchestration: Helm, Kubernetes
• Custom Solutions: Custom Grain, Shell

In this section

• Stack Automation's Blueprint YAML
• The Ansible Grain
• The ArgoCD Grain
• The Blueprint Grain
• The CDK Grain
• The CloudFormation Grain​
• The CloudShell Grain
• The Helm Grain
• The Kubernetes Grain​
• The OpenTofu Grain
• The Terraform Grain
• The Terragrunt Grain
• The Shell Grain
• Custom Grain