CI/CD pipelines with Terraform Cloud

Sam Lee, Solutions Engineer at HashiCorp, will show you how you can utilize the HashiCorp CI/CD pipeline integration tool for Terraform Cloud to accelerate your terraform development workflows. Sign up for a free Terraform Cloud account → www.hashicorp.com/products/te...
Subscribe to our CZcams Channel → czcams.com/users/HashiCorp?s...
For hands-on interactive labs, visit HashiCorp Developer → developer.hashicorp.com/
HashiCorp provides infrastructure automation software for multi-cloud environments, enabling enterprises to unlock a common cloud operating model to provision, secure, connect, and run any application on any infrastructure. HashiCorp tools Vagrant, Packer, Terraform, Vault, Consul, Nomad, Boundary, and Waypoint allow organizations to deliver applications faster by helping enterprises transition from manual processes and ITIL practices to self-service automation and DevOps practices.
For more information → hashicorp.com
Twitter → / hashicorp
LinkedIn → / hashicorp
Facebook → / hashicorp

[@samys288]

Thank you Sam, excellent video!. I would like ask you 2 things; from the point of view of the maintainer the source code; using the API Workflow approach can be more complex in the time? the another question is when your using Sentinel for evaluate the any rule before to do the merge, what happen if the rule return: false, then the pull request will fail too?

[@HashiCorp]

1. Yes - API Workflow is a more complex approach, which is why we need to consider at least the three key questions before we dive into such approach:
a. What is the use-case that we’re solving that requires a CI/CD workflow?
b. Can our use-case be resolved through alternative workflows like VCS?
c. Do we have the resources to implement and maintain an API-driven workflow?
API driven is not meant to be simple, it’s meant to give us substantial amount of flexibility for the use-case we’re trying to resolve.
2. If the rule returns “False”, the speculative plan from Terraform Cloud will fail - and the pull request will have a failed check. This is intended because it provides us a feedback loop.
For further information, please refer to: support.hashicorp.com/hc/en-us/articles/360000484507-Resolving-a-PR-plan-failure

[@samys288]

Thank you Sam!

[@vitbyst]

I would use a Beginner -> Pro -> Expert level sequence