21800 Commits (0a6938e90a104fce1da1d6c97f0a3f386b030d64)

 

All Branches   

Search

Author	SHA1	Message	Date
James Bardin	0a6938e90a	update tests to match pre-release constraint rules	7 years ago
James Bardin	398a6ef31a	update go-version ... The latest go-version update properly handles pre-release versions in constraints.	7 years ago
Martin Atkins	618883596a	command: remove "terraform push" ... The remote API this talks to will be going away very soon, before our next major release, and so we'll remove the command altogether in that release. This also removes the "encodeHCL" function, which was used only for adding a .tfvars-formatted file to the uploaded archive.	7 years ago
Martin Atkins	c51d22bdeb	config/hcl2shim: don't put nils in ConfigValue maps ... Absent values are omitted by the old code we are emulating in HCL, so we must do the same here in order to avoid breaking assumptions in the helper/schema layer.	7 years ago
Martin Atkins	860a57d104	tfdiags: Simple helper for creating "sourceless" diagnostics ... While diagnostics are primarily designed for reporting problems in configuration, they can also be used for errors and warnings about the environment Terraform is running in, such as inability to reach a remote service, etc. Function Sourceless makes it easy to produce such diagnostics with the customary summary/detail structure. When these diagnostics are rendered they will have no source code snippet and will instead just include the English-language content.	7 years ago
Martin Atkins	9bd47bf17c	tfdiags: helper functions for nicer display of cty.PathError ... cty doesn't have a native string representation of a cty.Path because it is the layer below any particular syntax, but up here in Terraform land we know that we use HCL native syntax and so we can format a string in a HCL-ish way for familiarity to the user. We'll use this form automatically when such an error is used directly as a diagnostic, but we also expose the function publicly so that other code that incorporates errors into diagnostic detail strings can apply the same formatting.	7 years ago
Martin Atkins	e309675853	tfdiags: Contextual diagnostics ... The usual usage of diagnostics requires us to pass around source location information to everywhere that might generate a diagnostic, and that is always the best way to get the most precise diagnostic source locations. However, it's impractical to require source location information to be retained in every Terraform subsystem, and so this new idea of "contextual diagnostics" allows us to separate the generation of a diagnostic from the resolution of its source location, instead resolving the location information as a post-processing step once the call stack unwinds to a place where there is enough context to find it. This is necessarily a less precise approach than reading the source ranges directly from the configuration AST, but gives us an alternative to no diagnostics at all in portions of Terraform where full location information is not available. This is a best-effort sort of thing which will get as precise as it can but may return a range in a parent block if the precise location of a particular attribute cannot be found. Diagnostics that rely on this mechanism should include some other contextual information in the detail message to make up for any loss of precision that results.	7 years ago
Martin Atkins	b41f08d79d	govendor fetch github.com/zclconf/go-cty/...	7 years ago
James Bardin	a79d620f03	remove legacy remote state code	7 years ago
James Bardin	979faa5dbe	move artifactory remote state to backend	7 years ago
James Bardin	178eb6076e	remove legacy remote file code ... This code is not referenced at all	7 years ago
James Bardin	18ef072325	move legacy http remote state to a backend	7 years ago
James Bardin	3595bd3f81	remove dead legacy gcs code	7 years ago
James Bardin	fe527ec9d7	move legacy etcd remote state to a backend	7 years ago
Martin Atkins	9a004e3f9d	command: "terraform validate" JSON support ... In the long run we'd like to offer machine-readable output for more commands, but for now we'll just start with a tactical feature in "terraform validate" since this is useful for automated testing scenarios, editor integrations, etc, and doesn't include any representations of types that are expected to have breaking changes in the near future.	7 years ago
Martin Atkins	bfd9392eb8	command: beginnings of new config loader in "terraform validate" ... As part of some light reorganization of our commands, this new implementation no longer does validation of variables and will thus avoid the need to spin up a fully-valid context. Instead, its focus is on validating the configuration itself, regardless of any variables, state, etc. This change anticipates us later adding a -validate-only flag to "terraform plan" which will then take over the related use-case of checking if a particular execution of Terraform is valid, _including_ the state, variables, etc. Although leaving variables out of validate feels pretty arbitrary today while all of the variable sources are local anyway, we have plans to allow per-workspace variables to be stored in the backend in future and at that point it will no longer be possible to fully validate variables without accessing the backend. The "terraform plan" command explicitly requires access to the backend, while "terraform validate" is now explicitly for local-only validation of a single module. In a future commit this will be extended to do basic type checking of the configuration based on provider schemas, etc.	7 years ago
Martin Atkins	fd5b7b42b8	command: new Meta methods for accessing the new config loader ... We need to share a single config loader across all callers because that allows us to maintain the source code cache we'll use for snippets in error messages. Nothing calls this yet. Callers will be gradually updated away from Module and Config in subsequent commits.	7 years ago
Martin Atkins	bd10b84a8e	command/format: include source snippets in diagnostics ... If we get a diagnostic message that references a source range, and if the source code for the referenced file is available, we'll show a snippet of the source code with the source range highlighted. At the moment we have no cache of source code, so in practice this codepath can never be visited. Callers to format.Diagnostic will be gradually updated in subsequent commits.	7 years ago
Martin Atkins	fff2ed1d7e	Update CHANGELOG.md	7 years ago
Martin Atkins	6a6d21fb0a	version: change to 0.12.0 to mark the beginning of the 0.12 dev branch	7 years ago
Sander van Harmelen	2b128f3bfb	Update CHANGELOG.md	7 years ago
Sander van Harmelen	6d4dffb93e	Merge pull request #19088 from hashicorp/f-plan-policy ... backend/remote: make sure we also output policies while planning	7 years ago
Luke Kysow	3eafbf3861	Add link to Terraform's GitHub Actions docs (#19091)	7 years ago
Sander van Harmelen	8875fa660f	Make sure we also output policies while planning	7 years ago
Paul Tyng	87d05607d3	Add missing Azure entry to changelog	7 years ago
Sander van Harmelen	3d3c748ffe	release: clean up after v0.11.9-beta1	7 years ago
Sander van Harmelen	48c1ae62b3	v0.11.9-beta1	7 years ago
Sander van Harmelen	7e4bff54cd	Merge pull request #19079 from hashicorp/f-header ... backend/remote: improve console output	7 years ago
Sander van Harmelen	775f8a9626	Make sure we always set a custom header ... This is for TFE to recognize were the calls come from.	7 years ago
Sander van Harmelen	0a59e54933	Improve the output just a bit	7 years ago
Sander van Harmelen	cdf997a97c	govendor: update `go-tfe`	7 years ago
Paul Tyng	f74774ff4f	Merge pull request #18877 from gsacavdm/update-goautorest ... Update go-autorest to v9.10.0	7 years ago
Sander van Harmelen	7b55d1640e	Merge pull request #19060 from hashicorp/f-stx-etx ... backend/remote: update `go-tfe` to support better log polling	7 years ago
Sander van Harmelen	c08cd597c5	Omit any empty lines containing STX/ETX markers	7 years ago
Sander van Harmelen	8826d67acf	govendor: update `go-tfe`	7 years ago
Sander van Harmelen	5e511e1ea1	Update CHANGELOG.md	7 years ago
Sander van Harmelen	c3e9d78873	Merge pull request #19047 from hashicorp/f-watch-queues ... backend/remote: print status updates while waiting for the run to start	7 years ago
Sander van Harmelen	fb0af07696	Print status updates while waiting for the run to start	7 years ago
Sander van Harmelen	62656a6ce8	Update CHANGELOG.md	7 years ago
Sander van Harmelen	56e6c60f76	Merge pull request #18533 from alice-sawatzky/master ... change chef linux provisioner to use user:group chown syntax	7 years ago
Sander van Harmelen	5eb49f9df5	govendor: update `go-tfe`	7 years ago
Sander van Harmelen	617aaa6839	Update CHANGELOG.md	7 years ago
Sander van Harmelen	4586b9f65a	Merge pull request #19035 from hashicorp/f-policy-override ... backend/remote: don’t ask questions when -auto-approve is set	7 years ago
Chris Griggs	15dda63358	Merge pull request #19044 from cgriggs01/cgriggs01-add-helm ... add helm links	7 years ago
cgriggs01	87191d46cd	add helm links	7 years ago
Chris Griggs	af2e504296	Merge pull request #19039 from cgriggs01/cgriggs01-nutanix-links ... [Website] New Nutanix Provider Links	7 years ago
cgriggs01	24c360ec8d	add nutanix links	7 years ago
Sander van Harmelen	d78470ad5a	Don’t ask questions when -auto-approve is set ... We previously asked to override a soft-failed policy, even wehn -auto-approve was set. That is now fixed by returning a policy failed error.	7 years ago
Sander van Harmelen	4ff43440be	Update CHANGELOG.md	7 years ago
Sander van Harmelen	53a8aaaf85	Merge pull request #19022 from hashicorp/f-auto-apply ... backend/remote: properly handle workspaces that auto apply changes	7 years ago