21440 Commits (e66e65ccd9e435ca62359e68d0dbcaa1382295ff)

 

All Branches   

Search

Author	SHA1	Message	Date
Martin Atkins	e66e65ccd9	configs: Export MergeBodies and new SynthBody function ... We have a few special use-cases in Terraform where an object is constructed from a mixture of different sources, such as a configuration file, command line arguments, and environment variables. To represent this within the HCL model, we introduce a new "synthetic" HCL body type that just represents a map of values that are interpreted as attributes. We then export the previously-private MergeBodies function to allow the synthetic body to be used as an override for a "real" body, which then allows us to combine these various sources together while still retaining the proper source location information for each individual attribute. Since a synthetic body doesn't actually exist in configuration, it does not produce source locations that can be turned into source snippets but we can still use placeholder strings to help the user to understand which of the many different sources a particular value came from.	8 years ago
Martin Atkins	34229ab331	configschema: include description in schema ... We will need access to this information in order to render interactive input prompts, and it will also be useful in returning schema information to external tools such as text editors that have autocomplete-like functionality.	8 years ago
James Bardin	936ad25e9f	update tests to match pre-release constraint rules	8 years ago
James Bardin	2ab943fbd4	update go-version ... The latest go-version update properly handles pre-release versions in constraints.	8 years ago
Martin Atkins	8c93532871	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.	8 years ago
Martin Atkins	26430a19de	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.	8 years ago
Martin Atkins	b43690c01a	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.	8 years ago
Martin Atkins	3cc7343eee	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.	8 years ago
Martin Atkins	f17a582d2b	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.	8 years ago
Martin Atkins	80e83fed7b	govendor fetch github.com/zclconf/go-cty/...	8 years ago
James Bardin	6ed5d88888	remove legacy remote state code	8 years ago
James Bardin	39c83a294a	move artifactory remote state to backend	8 years ago
James Bardin	15deef71a3	remove legacy remote file code ... This code is not referenced at all	8 years ago
James Bardin	a7d8a9d579	move legacy http remote state to a backend	8 years ago
James Bardin	bfb581f630	remove dead legacy gcs code	8 years ago
James Bardin	4f712b8d3c	move legacy etcd remote state to a backend	8 years ago
Martin Atkins	a29cea921e	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.	8 years ago
Martin Atkins	807887d708	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.	8 years ago
Martin Atkins	f66f7a5441	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.	8 years ago
Martin Atkins	5154368676	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.	8 years ago
Martin Atkins	8a56db5f34	Update CHANGELOG.md	8 years ago
Martin Atkins	cffc00346a	version: change to 0.12.0 to mark the beginning of the 0.12 dev branch	8 years ago
Adit Sarfaty	dfa623250a	helper/validation: IP address and IP address range validation helpers	8 years ago
Martin Atkins	d4eb6049b3	Update CHANGELOG.md	8 years ago
Martin Atkins	5659128126	repl: fix formatting of list and map values ... The indent function was stripping out newlines, causing multi-element lists and maps to be rendered incorrectly. We were also not quoting strings in these nested structures, leading to weird behavior if any expression punctuation or newlines were present in these strings. This part of Terraform will get a more serious overhaul as part of switching to the new parser/interpreter implementation but this is a tactical fix to make the results of this command more usable in the short term.	8 years ago
James Bardin	68ff5f767c	Merge pull request #17700 from ScottWinkler/master ... Fix scrub mistake	8 years ago
James Bardin	545e77e184	Merge pull request #17711 from hashicorp/jbardin/cleanup-temps ... cleanup temp files	8 years ago
James Bardin	e980156451	cleanup temp files from command tests ... Rather than try to modify all the hundreds of calls to the temp helper functions, and cleanup the temp files at every call site, have all tests work within a single temp directory that is removed at the end of TestMain.	8 years ago
James Bardin	15dc75720e	don't re-use a TempDir path ... Rather than creating and immediately removing a temp directory to get a random path name, fetch files into a subdirectory.	8 years ago
James Bardin	28c46d1a90	cleanup temp files from backend tests	8 years ago
Martin Atkins	0a5059df15	website: Stronger statements on when to use named workspaces ... In an earlier commit we added the "Best Practices" situation to try to clarify the intended uses of named workspaces and to warn against using them as an alternative to system decomposition. However, the prior statement was cautious in its recommendations in the interests of being pragmatic, and as a result we've seen that users have in some cases misunderstood or disregarded these recommendations. The new "When to use Multiple Workspaces" section aims to be more explicit that having multiple separate Terraform configurations is the preferred solution for many use-cases, and that workspaces are intended for a more limited set of use-cases around convenient development and testing. It also emphasizes the analogy to version control branches that was just a footnote in the prior text, to help the reader become familiar with the concept by relating it to a concept and workflow they are hopefully already familiar with. This new section also attempts to provide a more elaborate description of the proposed alternative when the goal is system decomposition. In the long run some of this content would probably be better placed elsewhere since it is useful advice even for users who never discover named workspaces, but it can live here for the time being to limit the scope of this change until we are ready to make more comprehensive revisions to the docs in this area. Finally, the introductory documentation here is adjusted slightly in preparation for the intended future expansion of workspaces to include stored variable values and, for more tailored backends like Terraform Enterprise, a full log of prior operations. More revisions will be required to cover the specifics of this later, but this new framing will hopefully help users form a mental model of named workspaces that has room for these future enhancements and the corresponding concept in Terraform Enterprise, rather than our previous framing that workspaces are fundamentally just named states.	8 years ago
ScottWinkler	f043954352	Fix scrub mistake ... Fixed a bug in which an example custom provider would be saved as "terraform-provider-custom-v0.0.1" instead of "terraform-provider-custom_v0.0.1". Not an issue when running the bundle on TFE, but a problem when trying to run a terraform bundle locally.	8 years ago
Masayuki Morita	1e2bb07504	command: Restore `auto-approve` flag in the output of `apply -help`	8 years ago
AV Jafrey	725281f4aa	website: Fix typo in the provider development program guide	8 years ago
James Bardin	e9e4ee4940	Merge pull request #17609 from hashicorp/jbardin/remote-command ... clean up remote.Cmd api	8 years ago
Matthew Frahry	fe84adb5f8	Merge pull request #17685 from hashicorp/cherry-pick-oraclepaas ... Cherry pick oraclepaas	8 years ago
Matthew Frahry	7c66624177	Update major-index.html.markdown	8 years ago
Matthew Frahry	ddb9af57dc	Update index.html.markdown	8 years ago
Matthew Frahry	17dbe1a835	Merge pull request #17682 from cgriggs01/master ... add oracle pass links	8 years ago
Chris Griggs	fd43298ffe	Update major-index.html.markdown	8 years ago
Chris Griggs	441194b396	fixes	8 years ago
Matthew Frahry	c44e901bf0	Update index.html.markdown	8 years ago
Chris	043c74178f	add oracle pass links	8 years ago
James Bardin	ad8642e2c2	have remote.ExitError format errors and status ... Since all use cases of ExitStatus are just putting it into fmt.Errorf, usually with the command string, have ExitStatus do that for the caller.	8 years ago
James Bardin	c8ce63fc16	Merge pull request #17658 from NikkeiFTLearning/homeDir-build-in-method ... Use built-in method to get user homedir instead of eval on sh	8 years ago
James Bardin	0c39b69d50	Merge pull request #17674 from hashicorp/jbardin/import-timeouts ... make sure ResourceData timeouts are always set	8 years ago
James Bardin	798df9dafa	make sure ResourceData timeouts are always set ... Return the global default timeout if the ResourceData timeouts are nil. Set the timeouts from the Resource when calling Resource.Data, so that the config values are always available.	8 years ago
James Bardin	a24ace68c8	release: clean up after v0.11.5	8 years ago
James Bardin	3b18741004	Merge branch 'master' into stable-website	8 years ago
James Bardin	342c529aa5	v0.11.5	8 years ago