Terraform - Infrastructure as Code
Find a file
Martin Atkins 3c14eeb945 stackeval: Make some provisioners available to stack components
This makes the built-in "remote-exec" and "file" provisioners available
for use in the modules that implement stack components. These are both
relatively easy and low-risk to include because they are builtins and
don't require anything from outside of Terraform itself.

For now this intentionally excludes local-exec because we'll want to think
about what constraints we want to put on it, if any, to help ensure we can
meet the goal of stack configurations being portable between different
execution environments without significant modification, and our current
stacks execution environment doesn't guarantee the availability of any
external software _at all_.

The motivation for adding this now is just to give some better feedback
when someone uses a module using one of these provisioners, since otherwise
they'll see just a confusing generic error message from the modules
runtime about the provisioners not being available. I expect we'll revisit
this later and consider expanding it to at least include local-exec, and
_maybe_ external provisioner plugins, although that's more questionable
because the provisioner plugin mechanism is incredibly legacy and doesn't
have any way to work outside of local Terraform CLI usage today.

There are no tests here yet because these provisioners are not mockable
and would depend on having an SSH or WinRM server to connect to. Later we
should ponder how to make this more testable, which might mean making
another part of the system responsible for actually providing the
provisioner factories and thus our tests here can use fakes. The goal here
is just to get this done in a relatively lightweight way for better
feedback during preview though, so we're not yet ready to make significant
time investments here.
2024-01-08 14:14:33 -08:00
.github Limiting lock behavior to issues and PRs; ignoring discussions. 2023-12-06 15:48:12 -08:00
.release Change release order of operations 2023-10-02 19:01:52 -07:00
docs Merge pull request #34367 from hashicorp/RELPLAT-955-EOY-license-updates 2024-01-02 09:20:56 -08:00
internal stackeval: Make some provisioners available to stack components 2024-01-08 14:14:33 -08:00
scripts Exit CD when fail for a variety of reasons 2023-10-27 17:06:39 -04:00
testing/equivalence-tests Update copyright file headers to BUSL-1.1 2023-08-10 23:43:27 +01:00
tools tfstackdata1: Protobuf schema for stack plan and state serialization 2023-11-15 12:38:52 -08:00
version update after cutting v1.7 branch 2023-12-06 12:59:20 -05:00
website Test mocks docs fixes (#34435) 2023-12-20 17:43:59 +00:00
.copywrite.hcl update year in license files 2023-12-06 11:58:53 -08:00
.gitignore Fix .gitignore terraform entry to be root-relative 2022-05-05 10:24:38 -04:00
.go-version move from Go 1.21.3 to 1.21.5 (various bug & security fixes) 2023-12-06 14:46:04 -08:00
.tfdev Remove revision from version command 2021-01-12 16:35:30 -05:00
BUGPROCESS.md Update BUGPROCESS.md 2023-03-18 17:14:20 -04:00
BUILDING.md elaborate further on experiments and cgo 2023-07-17 11:56:13 -07:00
CHANGELOG.md update after cutting v1.7 branch 2023-12-06 12:59:20 -05:00
checkpoint.go Update copyright file headers to BUSL-1.1 2023-08-10 23:43:27 +01:00
codecov.yml Update copyright file headers to BUSL-1.1 2023-08-10 23:43:27 +01:00
CODEOWNERS Update codeowner of gcs backend to include Strategic Integrations team (#31848) 2022-09-27 21:38:52 +01:00
commands.go adopt hashicorp/cli fork of mitchellh/cli (#34429) 2023-12-20 11:04:10 +00:00
copyright_headers.go stick with go generate check instead 2023-08-30 14:25:49 -07:00
Dockerfile Update copyright file headers to BUSL-1.1 2023-08-10 23:43:27 +01:00
experiments.go Update copyright file headers to BUSL-1.1 2023-08-10 23:43:27 +01:00
go.mod build(deps): bump github.com/cloudflare/circl from 1.3.3 to 1.3.7 (#34504) 2024-01-08 18:22:40 +00:00
go.sum build(deps): bump github.com/cloudflare/circl from 1.3.3 to 1.3.7 (#34504) 2024-01-08 18:22:40 +00:00
help.go adopt hashicorp/cli fork of mitchellh/cli (#34429) 2023-12-20 11:04:10 +00:00
LICENSE update year in license files 2023-12-06 11:58:53 -08:00
main.go adopt hashicorp/cli fork of mitchellh/cli (#34429) 2023-12-20 11:04:10 +00:00
main_test.go adopt hashicorp/cli fork of mitchellh/cli (#34429) 2023-12-20 11:04:10 +00:00
Makefile stick with go generate check instead 2023-08-30 14:25:49 -07:00
plugins.go Update copyright file headers to BUSL-1.1 2023-08-10 23:43:27 +01:00
provider_source.go Update copyright file headers to BUSL-1.1 2023-08-10 23:43:27 +01:00
README.md update licence link in README to BSL 2023-08-11 11:25:40 +02:00
signal_unix.go Update copyright file headers to BUSL-1.1 2023-08-10 23:43:27 +01:00
signal_windows.go Update copyright file headers to BUSL-1.1 2023-08-10 23:43:27 +01:00
staticcheck.conf Add staticcheck.conf to reduce unactionable noise in IDEs (#34036) 2023-10-12 11:01:12 -07:00
telemetry.go add missing copyright headers 2023-08-16 11:21:49 -07:00
tools.go run copyright header check recursively 2023-08-30 14:25:49 -07:00
version.go Update copyright file headers to BUSL-1.1 2023-08-10 23:43:27 +01:00
working_dir.go Update copyright file headers to BUSL-1.1 2023-08-10 23:43:27 +01:00

Terraform

Terraform

Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions.

The key features of Terraform are:

  • Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.

  • Execution Plans: Terraform has a "planning" step where it generates an execution plan. The execution plan shows what Terraform will do when you call apply. This lets you avoid any surprises when Terraform manipulates infrastructure.

  • Resource Graph: Terraform builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, Terraform builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.

  • Change Automation: Complex changesets can be applied to your infrastructure with minimal human interaction. With the previously mentioned execution plan and resource graph, you know exactly what Terraform will change and in what order, avoiding many possible human errors.

For more information, refer to the What is Terraform? page on the Terraform website.

Getting Started & Documentation

Documentation is available on the Terraform website:

If you're new to Terraform and want to get started creating infrastructure, please check out our Getting Started guides on HashiCorp's learning platform. There are also additional guides to continue your learning.

Show off your Terraform knowledge by passing a certification exam. Visit the certification page for information about exams and find study materials on HashiCorp's learning platform.

Developing Terraform

This repository contains only Terraform core, which includes the command line interface and the main graph engine. Providers are implemented as plugins, and Terraform can automatically download providers that are published on the Terraform Registry. HashiCorp develops some providers, and others are developed by other organizations. For more information, see Extending Terraform.

License

Business Source License 1.1