Source and Parameters
To configure the Terraform workflowβs source type, there are two options:
- Git Repository: Fetch code directly from private repositories using Git providers like GitHub or GitLab. Learn more about version control settings to set up repositories for Terraform configurations, especially useful for private repositories.
- Subscribed Templates: Use pre-built templates from the StackGuardian Library, enabling infrastructure deployment with a no-code interface.
Advanced Optionsβ
The following advanced setup options are available when Git Repository is enabled:
1.1 Referenceβ
Specify a Git branch, tag, or commit (e.g., main
, v1.0.0
) to fetch the exact code version needed for the workflow.
1.2 Working Directoryβ
Define the directory containing your Terraform configuration (e.g., infra
, app1/aws/ec2
). This is helpful when configurations are not stored in the root directory of the repository.
1.3 Git Sparse Checkout Configβ
Optimize large repositories by selectively checking out only the relevant paths. You can include/exclude paths using rules.
1.4 Enable git core.autocrlfβ
This option enables automatic line-ending conversion in Git across different operating systems (e.g., Windows, Unix) to prevent conflicts during Terraform plans.
Template Parametersβ
Choose how to provide inputs variables to a template, enabling parameterized terraform executions.
- Select a "Subscribed Template" to utilise
SG noCode
form to pass input variables to the template parameters,
- Available with source type "Subscribed Template" or "Git Repository", use
JSON-Formatted Input
to provide inputs in key-value format,