terraform

Commit Graph

Author	SHA1	Message	Date
cgriggs01	83e97fdbb5	Okta links + move venafi	7 years ago
Martin Atkins	f96edbb113	Revise our contributing/development documentation Our documentation for how to contribute was in quite a state of disrepair, with some documents still describing things as they were before moving providers into separate repositories, others making assumptions about Go development that are no longer true in modules mode, and so forth. This is an attempt at a reset to a good state that should work with the codebase as it currently stands, and should hopefully serve as a basis for iterative improvement from here. These new instructions lean primarily on standard Go toolchain usage and instruct using the Makefile only for some Terraform-specific situations that the Go toolchain does not automatically handle. The idea here is that this direct usage of primary commands in the Go toolchain is less likely to be broken by changes in future Go releases, and should be immediately familiar to anyone who has experience with Go development.	7 years ago
Kristin Laemmert	96af863065	command/validate: warn if unused flags are set on the command line (#22989 ) * command/validate: output a warning if unused flags are set The -var and -var-file command line flags are accepted, but not used, in `terraform validate`. This PR adds a warning for users who set either of those flags, so they know that setting them has no effect.	7 years ago
Radek Simko	9051591899	go mod tidy & go mod vendor	7 years ago
Radek Simko	cd21a3859d	Remove svchost package	7 years ago
Radek Simko	32f9722d9d	Replace import paths & set UA string where necessary	7 years ago
Martin Atkins	047733d20c	website: Full examples for for_each with flatten and setproduct A very common question since we launched the two repetition constructs is how to deal with situations where the input data structure doesn't match one-to-one with the desired configuration. This adds some full worked examples of two common situations that have come up in questions. To avoid adding a lot of extra content to the already-large "expressions" and "resources" pages, the main bulk of this new content lives with the relevant functions themselves as a full example of one thing they are good for, and then we'll link to them from the two general documentation sections where folks are likely to be reading when they encounter the problem.	7 years ago
Kristin Laemmert	0d27e8ca7d	Update CHANGELOG.md	7 years ago
Stas Alekseev	6656104f8f	deps: github.com/hashicorp/aws-sdk-go-base@v0.4.0 (#22994 )	7 years ago
Martin Atkins	cf16b42135	Update CHANGELOG.md	7 years ago
Martin Atkins	8664749b59	backend: Allow certain commands to opt out of required variable checks Terraform Core expects all variables to be set, but for some ancillary commands it's fine for them to just be set to placeholders because the variable values themselves are not key to the command's functionality as long as the terraform.Context is still self-consistent. For such commands, rather than prompting for interactive input for required variables we'll just stub them out as unknowns to reflect that they are placeholders for values that a user would normally need to provide. This achieves a similar effect to how these commands behaved before, but without the tendency to produce a slightly invalid terraform.Context that would fail in strange ways when asked to run certain operations.	7 years ago
Martin Atkins	e21f0fa61e	backend/local: Handle interactive prompts for variables in UI layer During the 0.12 work we intended to move all of the variable value collection logic into the UI layer (command package and backend packages) and present them all together as a unified data structure to Terraform Core. However, we didn't quite succeed because the interactive prompts for unset required variables were still being handled _after_ calling into Terraform Core. Here we complete that earlier work by moving the interactive prompts for variables out into the UI layer too, thus allowing us to handle final validation of the variables all together in one place and do so in the UI layer where we have the most context still available about where all of these values are coming from. This allows us to fix a problem where previously disabling input with -input=false on the command line could cause Terraform Core to receive an incomplete set of variable values, and fail with a bad error message. As a consequence of this refactoring, the scope of terraform.Context.Input is now reduced to only gathering provider configuration arguments. Ideally that too would move into the UI layer somehow in a future commit, but that's a problem for another day.	7 years ago
Martin Atkins	564b57b1f6	core: Require variables correctly set during NewContext We previously deferred this to Validate, but all of our operations require a valid set of variables and so checking this up front makes it more obvious when a call into Terraform Core from the CLI layer isn't populating variables correctly, instead of having it fail downstream somewhere. It's the caller's responsibility to ensure that it has collected values for all of the variables in some way before calling NewContext, because in the main case driven by the CLI there are many different places that variable values can be collected from and so handling the main user-facing validation in the CLI allows us to return better error messages that take into account which way a variable is (or is not) being set.	7 years ago
Jeff Green	e505845a63	command/apply: remove duplicate statement (#23011 )	7 years ago
Chris Griggs	b6257a3e26	Merge pull request #22997 from hashicorp/cgriggs01-venafi [Website] Add links to provider documentation	7 years ago
Pam Selle	03fa5cb7d6	Merge pull request #22966 from pselle/docs-splat Update expression docs to clarify for_each usage	7 years ago
Kristin Laemmert	241e88e5ed	Update CHANGELOG.md	7 years ago
Kristin Laemmert	a9da6f0e5b	command/jsonstate: properly marshal deposed resources (#23027 ) * command/jsonstate: properly marshal deposed resources This PR addresses 2 issues: `show -json` would crash if there was not a `Current` `states.ResourceInstance` for a given resource, and `deposed` resource instances were not shown at all. Fixes #22642	7 years ago
James Bardin	1ee851f256	Merge pull request #22846 from hashicorp/jbardin/evaluate-resource Always evaluate resources in their entirety	7 years ago
James Bardin	bfce78064b	lang/eval: more evalContext fixups self references do not need to be added to `managedResource`, and in fact that could cause issues later if self is allowed in contexts other than managed resources. Coalesce 2 cases in the Referenceable switch, be take the ContainingResource address of an instance beforehand.	7 years ago
Pam Selle	d6983eaaff	Update CHANGELOG.md	7 years ago
Pam Selle	43c66c2048	Merge pull request #22811 from notchairmk/b-apply-node-removed-targeted bug: fix terraform trying to clean up orphan modules on target	7 years ago
Pam Selle	2a50bc6b5a	More in expressions, removed extra resource thing	7 years ago
Pam Selle	67e314dcbe	Some docs updates to clarify splat confusion	7 years ago
tf-release-bot	dcb65fa9c7	Cleanup after v0.12.10 release	7 years ago
tf-release-bot	1c6e2a1eaf	v0.12.10	7 years ago
Nick Fagerlund	02d793f0ff	website / help: reconcile 'validate' command docs	7 years ago
Nick Fagerlund	f6e648cc8b	website: Document behavior of `self` object for provisioners	7 years ago
Martin Atkins	39e609d5fd	vendor: switch to HCL 2.0 in the HCL repository Previously we were using the experimental HCL 2 repository, but now we'll shift over to the v2 import path within the main HCL repository as part of actually releasing HCL 2.0 as stable. This is a mechanical search/replace to the new import paths. It also switches to the v2.0.0 release of HCL, which includes some new code that Terraform didn't previously have but should not change any behavior that matters for Terraform's purposes. For the moment the experimental HCL2 repository is still an indirect dependency via terraform-config-inspect, so it remains in our go.sum and vendor directories for the moment. Because terraform-config-inspect uses a much smaller subset of the HCL2 functionality, this does still manage to prune the vendor directory a little. A subsequent release of terraform-config-inspect should allow us to completely remove that old repository in a future commit.	7 years ago
cgriggs01	8e1ee85e4e	Add venafi links	7 years ago
James Bardin	38b69c9784	Merge pull request #22979 from hashicorp/jbardin/ssh-reconnect copy client pointer for keep-alive loop	7 years ago
James Bardin	1ccf1bd9a2	Update communicator/ssh/communicator.go Co-Authored-By: Kristin Laemmert <mildwonkey@users.noreply.github.com>	7 years ago
James Bardin	bbde7e3e35	copy client pointer for keep-alive loop If a connection fails and attempts to reconnect after the keep-alive loop started, the client will be pulled out from under the keep-alive requests. Close over a local copy of the client, so that reconnecting doesn't race with the keepalive loop terminating.	7 years ago
Pam Selle	eb456df411	Merge pull request #22951 from ialidzhikov/enh/remove-check-variables-flag Remove -check-variables flag from the docs	7 years ago
Pam Selle	e6795556f3	Update CHANGELOG.md	7 years ago
Pam Selle	b40385772e	Merge pull request #22705 from kmott/habitat-provisioner-updates Habitat provisioner updates	7 years ago
Paul Thrasher	6f313abc9e	Merge pull request #22761 from hashicorp/pault/tfce-ga Remote Backend: Support latest cost-estimate API	7 years ago
Paul Thrasher	f2ef8ef317	slow down tfce polling to 1s Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Paul Thrasher	4e308ef362	typos. some code, some text. Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
ialidzhikov	57ecc304e1	Remove -check-variables flag from the docs Signed-off-by: ialidzhikov <i.alidjikov@gmail.com>	7 years ago
Katy Moe	2c44a7aacb	remove dotfile exclusion in copyDir copyDir is used in configload/getter.go to copy previously downloaded modules instead of using the go-getter client every time. The go-getter client downloads dotfiles, but copyDir did not copy dotfiles, leading to inconsistent behaviour when reusing the same module source.	7 years ago
Kyle Mott	30895a6cf5	Merge cleanup, remove `license` parameter in favor of bool `accept_license`, adjust how license acceptance is done, update hab provisioner doc.	7 years ago
Kyle Mott	e3d1876f44	Merge upstream	7 years ago
Paul Thrasher	d2eaffabea	vendor latest go-tfe Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Paul Thrasher	d3fc3dee6e	clean up go mod for go-tfe Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Paul Thrasher	e2831b3d1e	tfce test additions Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Paul Thrasher	bc2d888b7b	update to go-tfe 0.3.23 this fixes the attr types Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Paul Thrasher	39817ac476	cost estimation status polling Properly wait for cost estimation to finish running before outputting the results. Waits 500 milliseconds between checks, rather than backing off exponentially, because we are not in a run queue. At the point we're waiting, we expect cost estimation to be run in a timely manner.	7 years ago
Paul Thrasher	29c8ca485e	go-tfe dep update to 0.3.22 Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago
Paul Thrasher	979bba0f32	tfce mock fix Signed-off-by: Paul Thrasher <pthrasher@hashicorp.com>	7 years ago

1 2 3 4 5 ...

24954 Commits (ba7679b6791a306a73062ddd5a00359452e152fc) All Branches Search

24954 Commits (ba7679b6791a306a73062ddd5a00359452e152fc)

All Branches