Go to file
Martin Atkins 01b22f4b76 command/e2etest: TestProviderTampering
We have various mechanisms that aim to ensure that the installed provider
plugins are consistent with the lock file and that the lock file is
consistent with the provider requirements, and we do have existing unit
tests for them, but all of those cases mock our fake out at least part of
the process and in the past that's caused us to miss usability
regressions, where we still catch the error but do so at the wrong layer
and thus generate error message lacking useful additional context.

Here we'll add some new end-to-end tests to supplement the existing unit
tests, making sure things work as expected when we assemble the system
together as we would in a release. These tests cover a number of different
ways in which the plugin selections can grow inconsistent.

These new tests all run only when we're in a context where we're allowed
to access the network, because they exercise the real plugin installer
codepath. We could technically build this to use a local filesystem mirror
or other such override to avoid that, but the point here is to make sure
we see the expected behavior in the main case, and so it's worth the
small additional cost of downloading the null provider from the real
registry.
2021-10-05 10:59:59 -07:00
.circleci build: Add exhaustive switch statement lint 2021-09-24 15:12:44 -04:00
.github Add clarification to message about community PR review 2021-09-07 21:04:13 -05:00
docs Add docs on how to release a new major protocol version. (#29552) 2021-09-09 11:33:07 -07:00
internal command/e2etest: TestProviderTampering 2021-10-05 10:59:59 -07:00
scripts build: Add exhaustive switch statement lint 2021-09-24 15:12:44 -04:00
tools build: Add exhaustive switch statement lint 2021-09-24 15:12:44 -04:00
version Cleanup after v1.1.0-alpha20210922 release 2021-09-22 18:12:02 +00:00
website Update publish.html.md (#29671) 2021-09-29 13:42:54 -07:00
.gitignore Remove several ignore rules 2021-09-01 14:37:26 -05:00
.go-version Upgrade to Go 1.17.1 2021-09-22 10:31:31 -07:00
.tfdev Remove revision from version command 2021-01-12 16:35:30 -05:00
BUGPROCESS.md Update BUGPROCESS.md 2020-12-10 12:15:39 -05:00
CHANGELOG.md Update CHANGELOG.md 2021-10-01 14:50:36 -07:00
CODEOWNERS etcdv3 backend is unmaintained 2021-07-20 13:59:08 -04:00
Dockerfile switch to hashicorp docker mirror 2020-10-29 22:37:11 -04:00
LICENSE Adding license 2014-07-28 13:54:06 -04:00
Makefile build: Add exhaustive switch statement lint 2021-09-24 15:12:44 -04:00
README.md Update README.md 2021-06-10 02:43:23 +02:00
checkpoint.go Move command/ to internal/command/ 2021-05-17 14:09:07 -07:00
codecov.yml update to match new default branch name (#27909) 2021-02-24 13:36:47 -05:00
commands.go workdir: Start of a new package for working directory state management 2021-09-10 14:56:49 -07:00
go.mod build: Add exhaustive switch statement lint 2021-09-24 15:12:44 -04:00
go.sum build: Add exhaustive switch statement lint 2021-09-24 15:12:44 -04:00
help.go Update links to CLI docs in code comments, messages, and readme 2021-01-22 12:22:21 -08:00
main.go Small comment typo 2021-06-24 16:41:58 -04:00
main_test.go don't error when processing autocomplete commands 2021-03-31 13:28:08 -04:00
plugins.go Move command/ to internal/command/ 2021-05-17 14:09:07 -07:00
provider_source.go Move command/ to internal/command/ 2021-05-17 14:09:07 -07:00
signal_unix.go Upgrade to Go 1.17 2021-08-17 15:20:05 -07:00
signal_windows.go Upgrade to Go 1.17 2021-08-17 15:20:05 -07:00
version.go Remove revision from version command 2021-01-12 16:35:30 -05:00
working_dir.go workdir: Start of a new package for working directory state management 2021-09-10 14:56:49 -07:00

README.md

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, see the introduction section of 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.

To learn more about compiling Terraform and contributing suggested changes, please refer to the contributing guide.

To learn more about how we handle bug reports, please read the bug triage guide.

License

Mozilla Public License v2.0