19777 Commits (4e85f552e79f0e9f9cfc0688ef4dc3e66cdad928)

 

All Branches   

Search

Author	SHA1	Message	Date
Radek Simko	4e85f552e7	Merge pull request #15246 from hashicorp/b-fix-cmd-provider-crash ... command/providers: Avoid crash when no configs found	9 years ago
James Bardin	a30007b41d	Merge pull request #15032 from hashicorp/jbardin/init ... change init args to remove source copy	9 years ago
Clint	458cac7f49	Update ISSUE_TEMPLATE (#15222) ... * Update ISSUE_TEMPLATE Update ISSUE_TEMPLATE to direct people to new split providers * Create ISSUE_TEMPLATE.md More loud * Update ISSUE_TEMPLATE.md * Create ISSUE_TEMPLATE.md * Create ISSUE_TEMPLATE.md moved to the top	9 years ago
Radek Simko	f5ff67c530	command/providers: Add regression test	9 years ago
Radek Simko	ee30df3efd	command/providers: Enable processing of meta-parameters ... This will enable proper colouring of the output, like for other commands.	9 years ago
Radek Simko	86fbcfac83	command/providers: Avoid crash when no configs found	9 years ago
Paul Stack	e50a57bcb7	Update CHANGELOG	9 years ago
Paul Stack	f7b5d536a4	Create CHANGELOG.md	9 years ago
Martin Atkins	5f24491ea6	Update CHANGELOG.md ... Some initial notes on the core/provider split for those following along with commits. More elaborate documentation will follow as the 0.10 release gets closer.	9 years ago
Martin Atkins	fc56f13f1f	Create CHANGELOG.md	9 years ago
Martin Atkins	698c22c924	Merge #14952: rename "state environments" to "workspaces"	9 years ago
Martin Atkins	f7ce6a15f8	backend: Operation.Environment renamed to "Workspace" ... This is part of an effort to switch this terminology across all of Terraform.	9 years ago
Martin Atkins	5a57962a32	website: replace "env" command docs with "workspace" command docs ... We are replacing this terminology. The old command continues to work for compatibility, but is deprecated. The docs should reflect the currently-recommended form.	9 years ago
Martin Atkins	418a8a8bc9	command + backend: rename various API objects to "Workspace" terminology ... We're shifting terminology from "environment" to "workspace". This takes care of some of the main internal API surface that was using the old terminology, though is not intended to be entirely comprehensive and is mainly just to minimize the amount of confusion for maintainers as we continue moving towards eliminating the old terminology.	9 years ago
Martin Atkins	33a266d61c	provider/terraform: "workspace" argument instead of "environment" ... We are moving away from using the term "environment" to describe separate named states for a single config, using "workspace" instead. The old attribute name remains supported for backward compatibility, but is marked as deprecated.	9 years ago
Martin Atkins	3be1d3148b	website: documentation for state workspaces ... This replaces the previous documentation on "State Environments", as part of our intentional terminology shift.	9 years ago
Martin Atkins	d4e5abe0eb	core: terraform.env variable is now terraform.workspace ... As part of our terminology shift, the interpolation variable for the name of the current workspace changes to terraform.workspace. The old name continues to be supported for compatibility. We can't generate a deprecation warning from here so for now we'll just silently accept terraform.env as an alias, but not mention it at all in the error message in the hope that its use phases out over time before we actually remove it.	9 years ago
Martin Atkins	5f9f13ab8f	command: show warnings from backend config validation ... Previously we just silently ignored warnings from validating the backend config, but now that we have a deprecated argument it's important to print these out so users can respond to the deprecation warning.	9 years ago
Martin Atkins	5026e1d313	backend/local: "environment_dir" renamed to "workspace_dir" ... As part of switching our terminology, we begin a deprecation cycle for "environment_dir" and advise users to switch to "workspace_dir" instead.	9 years ago
Martin Atkins	31d556894f	command: shallow UI-focused rename of "environment" to "workspace" ... Feedback after 0.9 was that the term "environment" was confusing due to it colliding with several other concepts, such as OS environment variables, a non-aligned Terraform Enterprise concept, and differing ideas of "environment" within various organizations. This new term "workspace" is intended to ease some of that confusion. This term is not used anywhere else in Terraform today, and we expect it to not be used in a manner that would be confusing within user organizations. This begins a deprecation cycle for the "terraform env" family of commands, instead moving to an equivalent set of "terraform workspace" commands. There are some remaining references to the old "environment" concept in the code, which will be cleaned up in a separate change. This change is instead focused on text visible in the UI and wording within code comments for the benefit of human maintainers of the code.	9 years ago
David Glasser	c25d848ffb	core: allow overriding environment name via env var ... This allows you to run multiple concurrent terraform operations against different environments from the same source directory. Fixes #14447. Also removes some dead code which appears to do the same thing as the function I modified.	9 years ago
James Bardin	2bfcdbbd08	change init args to remove source copy ... When init was modified in 0.9 to initialize a terraform working directory, the legacy behavior was kept to copy or fetch module sources. This left the init command without the ability that the plan and apply commands have to target a specific directory for the operation. This commit removes the legacy behavior altogether, and allows init to target a directory for initialization, bringing it into parity with plan and apply. If one want to copy a module to the target or current directory, that will have to be done manually before calling init. We can later reintroduce fetching modules with init without breaking this new behavior, by adding the source as an optional second argument. The unit tests testing the copying of sources with init have been removed, as well as some out of date (and commented out) init tests regarding remote states.	9 years ago
James Bardin	73139ba6aa	Merge pull request #15208 from hashicorp/0.10-plugins ... 0.10 Core/Provider split work	9 years ago
James Bardin	d1c50efb01	change providers.json to lock.json ... It might not just be for providers, and it's in the plugins dir, so lock.json seems descriptive enough.	9 years ago
James Bardin	08592c2602	update plugin name in command test	9 years ago
James Bardin	840978b2d5	udpate to plugin name convention ... Names are case-insensitive, using lowercase by default.	9 years ago
James Bardin	1b201e67ea	fix releases path and protocol header ... Last minute change to the location of the binaries	9 years ago
James Bardin	a529b64cc8	better init error output ... Provide log-form message when a provider isn't found, along with the desired constraints.	9 years ago
James Bardin	fdbfc17fae	missing constraints passed erroniously ... ConstrainVersions was documented as returning nil, but it was instead returning an empty set. Use the Count() method to check for nil or empty. Add test to verify failed constraints will show up as missing.	9 years ago
James Bardin	283ae0c7c4	fix comment and add some logging in discovery	9 years ago
James Bardin	ea3d9c86ba	sort constraints for consistent output	9 years ago
James Bardin	190d5fae76	vendor x/net/html	9 years ago
Martin Atkins	55d5e8a689	website: initial v0.10 upgrade guide ... Further iteration of this will undoubtedly be needed before the final release, but this is a start.	9 years ago
Martin Atkins	98ef947ed1	website: correction of heading and usage in "providers" command docs	9 years ago
Martin Atkins	fb405ff296	website: new documentation about provider version configuration	9 years ago
Martin Atkins	766f8e5d64	command init: remove confusing uses of "environment" in the usage ... "environment" is a very overloaded term, so here we prefer to use the term "working directory" to talk about a local directory where operations are executed on a given Terraform configuration.	9 years ago
Martin Atkins	eaf5a62197	website: don't recommend to use "terraform init" to clone examples ... This form of "terraform init" is vestigial at this point and being phased out in 0.10. Something similar may return in a later version for installing modules from a more formal module library, but for now we are advising to use git manually to simplify the UX for "terraform init".	9 years ago
Martin Atkins	d9b8c3cac0	website: "Initialization" section in the getting started guide ... It's now required to run "terraform init" to get the provider plugins installed, so we need to mention that in the intro guide.	9 years ago
Martin Atkins	3c429b3628	command init: show log output for each provider plugin downloaded ... Each provider plugin will take at least a few seconds to download, so providing feedback about each one should make users feel less like Terraform has hung. Ideally we'd show ongoing progress during the download, but that's not possible without re-working go-getter, so we'll accept this as an interim solution for now.	9 years ago
Martin Atkins	1b673746fd	core: don't allow core or providers to change between plan and apply ... The information stored in a plan is tightly coupled to the Terraform core and provider plugins that were used to create it, since we have no mechanism to "upgrade" a plan to reflect schema changes and so mismatching versions are likely to lead to the "diffs didn't match during apply" error. To allow us to catch this early and return an error message that _doesn't_ say it's a bug in Terraform, we'll remember the Terraform version and plugin binaries that created a particular plan and then require that those match when loading the plan in order to apply it. The planFormatVersion is increased here so that plan files produced by earlier Terraform versions _without_ this information won't be accepted by this new version, and also that older versions won't try to process plans created by newer versions.	9 years ago
Martin Atkins	4571a16b15	command: remove Meta.forceProviderSHA256s ... This was added with the idea of using it to override the SHA256 hashes to match those hypothetically stored in a plan, but we already have a mechanism elsewhere for populating context fields from plan fields, so this is not actually necessary.	9 years ago
Martin Atkins	9aae06db97	command: update mockGetProvider.GetProvider for new interface ... The expected type was changed in the mainline code but the tests were not updated to match.	9 years ago
Martin Atkins	4ba20f9c1c	command init: show suggested constraints for unconstrained providers ... When running "terraform init" with providers that are unconstrained, we will now produce information to help the user update configuration to constrain for the particular providers that were chosen, to prevent inadvertently drifting onto a newer major release that might contain breaking changes. A ~> constraint is used here because pinning to a single specific version is expected to create dependency hell when using child modules. By using this constraint mode, which allows minor version upgrades, we avoid the need for users to constantly adjust version constraints across many modules, but make major version upgrades still be opt-in. Any constraint at all in the configuration will prevent the display of these suggestions, so users are free to use stronger or weaker constraints if desired, ignoring the recommendation.	9 years ago
Martin Atkins	f70318097a	config: fix provider version constraint validation ... Previously we were using the "semver" library to parse version constraints, but we switched over to go-version and encapsulated it inside our own plugin/discovery package to reduce dependency sprawl in the code. This particular situation was missed when updating references to the new path, which meant that our validation code disagreed with the rest of the code about what is considered a valid version constraint string. By using the correct function, we ensure that we catch early any invalid versions.	9 years ago
James Bardin	dbbafbd43f	clean up plugin fetching ... We can filter the allowed versions and sort them before checking the protocol version, that way we can just return the first one found reducing network requests.	9 years ago
James Bardin	e0f2235f66	update init command with new GetProvider signature ... GetProvider needs the plugin protocol version to be passed in	9 years ago
James Bardin	48d37131e0	more tests for fetching providers ... Extend the test reslease server to return the protocol version header and a dummy zip file for the provider. Test filtering the plugins by plugin protocol version and add a full GetProvder test.	9 years ago
James Bardin	5f053a2e64	refactor GetProvider ... Get provider needs to be provided with the plugin protocol version, because it can't be imported here directly. The plugin url types and methods were confusing; replace them with a few functions to format the urls.	9 years ago
James Bardin	8ad67991a5	check protocol version on plugins ... Verify that the plugin we're requesting has a compatible protocol version.	9 years ago
James Bardin	fdeb3d929c	Add Versions.Sort ... Sort versions from newest to oldest.	9 years ago