You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer, I want terraform apply to be run in CI/CD (on merges to master) so that I can have a guarantee that the files in the terraform/ folder match the configuration on the production cloud.
A big benefit from this is that I would (as a follow-up task) be able to re-map outputs from terraform apply to inputs to helm.
That would reduce duplication of variables between Terraform and Helm. There's also things that I currently hard-code in Helm that could become variables based on the terraform outputs (eg. the ingress ip).
The text was updated successfully, but these errors were encountered:
Currently, I run terraform apply from the terminal whenever I make changes. Terraform documentation on running in automation: https://learn.hashicorp.com/terraform/development/running-terraform-in-automation
As a developer, I want terraform apply to be run in CI/CD (on merges to master) so that I can have a guarantee that the files in the
terraform/
folder match the configuration on the production cloud.A big benefit from this is that I would (as a follow-up task) be able to re-map outputs from
terraform apply
to inputs to helm.That would reduce duplication of variables between Terraform and Helm. There's also things that I currently hard-code in Helm that could become variables based on the terraform outputs (eg. the ingress ip).
The text was updated successfully, but these errors were encountered: