161 Commits (cb5ce1d35ea016f7ea38aa0b9fc84fa85ed0bd19)

Author	SHA1	Message	Date
Kevin Fishner	b13945f53c	Merge pull request #16931 from nfagerlund/dec2017_private_git_modules ... docs: Clarify the use of private github repos with TFE	8 years ago
Nick Fagerlund	40fefbd5e8	docs: Clarify the use of private github repos with TFE ... The machine user/password approach is wrong for TFE; use SSH keys instead.	8 years ago
James Bardin	03ddb9134a	Merge pull request #16903 from rwcee/build-service-auth-token ... Adds "build_auth_token" option to Habitat Provisioner	8 years ago
Rob Campbell	29f70bc112	Adds build_auth_token to Habitat Provisioner ... First successful run with private origin and HAB_AUTH_TOKEN set Update struct, schema, and decodeConfig names to more sensible versions Cleaned up formatting Update habitat provisioner docs Remove unused unitstring	8 years ago
Maciej Skierkowski	4a3c65984a	Update not on TFE Module Registry availability	8 years ago
Martin Atkins	c729bdff43	website: guide for using the S3 backend with multiple AWS accounts ... Users commonly ask how the S3 backend can be used in an organization that splits its infrastructure across many AWS accounts. We've traditionally shied away from making specific recommendations here because we can't possibly anticipate the different standards and regulations that constrain each user. This new section attempts to describe one possible approach that works well with Terraform's workflow, with the goal that users make adjustments to it taking into account their unique needs. Since we are intentionally not being prescriptive here -- instead considering this just one of many approaches -- it deviates from our usual active writing style in several places to avoid giving the impression that these are instructions to be followed exactly, which in some cases requires the use of passive voice even though that is contrary to our documentation style guide. For similar reasons, this section is also light on specific code examples, since we do not wish to encourage users to just copy-paste the examples without thinking through the consequences.	8 years ago
Nolan Davidson	a50a383946	Additional work on the habitat provisioner. ... Signed-off-by: Nolan Davidson <ndavidson@chef.io>	8 years ago
Paul Banks	06f067b4e6	Update registry API docs with browse and search (#16846) ... * Verify discovery works without trailing slash on discovery URL * Update registry API docs with browse and search endpoints * Add sample request/responses * Add comment to test to indicate expecations * Fix typo * Remove trailing slash weirdness	8 years ago
Kevin Fishner	3538f832b0	website: update "atlas" backend to recommend using ATLAS_TOKEN environment variable	8 years ago
Andrew	d6b8e27086	website: Document required S3 IAM actions for S3 backend	8 years ago
Andrew	2b68f4393e	website: explanation of TF_VAR_ precedence ... Fixes #15595	8 years ago
Sander van Harmelen	aaedf255c3	backend/s3: allow skipping the region check (#16757) ... Without the possibility to skip this check, it’s not possible to use a custom region with a third-party service that mimicks the S3 API.	8 years ago
David Meyer	fe0cc3b0db	config: new "rsadecrypt" interpolation function ... The primary use-case is to decrypt windows passwords obtained from AWS, but this function is generic and may find other purposes too.	8 years ago
mizuno	01c1142589	config: new "timeadd" interpolation function	8 years ago
Nic Cope	5c58ef16f7	provider/terraform: deprecate "environment" in favor of "workspace"	8 years ago
Martin Atkins	ab2dc0d987	website: "terraform push" version matching requirement ... It's important to match the version of local Terraform with the remote Terraform version in Terraform Enterprise when using the "terraform push" command, or else the uploaded configuration package may not be compatible.	8 years ago
Allison Ravenhall	fe33661b59	website: update "terraform env" reference to "terraform workspace"	8 years ago
James Bardin	0891bd2c88	Merge pull request #16778 from MichaelKueller/patch-1 ... fixed typo	8 years ago
Cameron Childress	ae33b68e68	website: An example of referencing resources with "count"	8 years ago
David Celis	714169502a	website: note that plugin_cache_dir must already exist ... This directory is not automatically created by Terraform	8 years ago
Gregory McCue	b9aee64f3b	website: correct intro docs about terraform init -upgrade ... "-upgrade" was misspelled as "-update".	8 years ago
Michael Küller	f7aa22fd81	fixed typo	8 years ago
Alexandru Ungur	9f1a773655	website: fix broken link from resources to multiple provider instances	8 years ago
Dmitry Grigorenko (gitHUB)	27aa4cb6bf	website: fix documented naming scheme for provider plugins	9 years ago
Jordi Pàmies	6786c1361f	website: fix incorrect examples for the chunklist function	9 years ago
Martin Atkins	31ee29050e	website: US English spelling of "honor"	9 years ago
Martin Atkins	1da2464e72	website: further copyediting for "Providers within Modules" ... The differences between the implicit and explicit modes of passing provider configurations between modules are significant enough to warrant giving these approaches different names and describing them separately. This also includes documentation of the current limitation discussed in #16612, where explicit passing requires a proxy configuration block even for a _default_ provider configuration, because that limitation is being accepted for the 0.11.0 release to limit scope.	9 years ago
Paul Banks	2889eded3f	Tweaks to Registry Docs for 0.11 (#16663) ... * Registry 0.11 doc tweaks * Add changes for v0.11	9 years ago
Martin Atkins	40b7b4c133	website: Further clarification on how providers and modules interact ... The initial pass of this section had some remaining ambiguities, so this is a second revision that attempts to use terminology more consistently and to not some additional behaviors that were not described in the initial version.	9 years ago
Martin Atkins	f3a2165587	website: Use "Input Variable" as full term for var.foo ... We've historically been somewhat inconsistent in how we refer to the type of object defined by "variable" blocks in configuration. Parts of our documentation refer to them as "input variables" or just "variables", while our implementation refers to them as "user variables". Since Terraform Registry is now also referring to these as "Inputs", here we standardize on "Input Variable" as the fully-qualified name for this concept, with "variable" being a shorthand for this where context is obvious. Outside of this context, anything that can be referred to in an interpolation expression is generically known as a "variable", with Input Variables being just one kind, specified by the "var." prefix. While this terminology shift is not critical yet, it will become more important as we start to document the new version of the configuration language so we can use the generic meaning of "variable" there.	9 years ago
Martin Atkins	3d33a36bf6	website: update terminology used in provider config docs ... The bulk of the text on this page hasn't been revised for some time and so parts of it were using non-idiomatic terminology or not defining terms at all. The main goal of this revision is to standardize on the following terms: - "provider configuration" refers to a specific provider block in config, as a distinct idea from the provider _itself_, which is a singleton. - "Default" vs. "additional" provider configurations, distinguishing those without and with "alias" arguments respectively. These are named here so that we can use this terminology to describe the different behaviors of each for the purposes of provider inheritance between modules.	9 years ago
James Belchamber	ec2281106f	Adding documentation for all supported imports in the Heroku provider (#16312)	9 years ago
Dominik Lekse	323654a716	Fixed documentation of azurerm backend advanced access variables (#16552) ... Signed-off-by: Dominik Lekse <dominik@lekse.de>	9 years ago
Martin Atkins	3b180d7f8a	Merge #16543: Bring the "terraform" provider back into core	9 years ago
Paul Stack	002200b8f1	websites/workspaces: Add Manta to the list of workspace backends (#16545) ... As Manta backend has now been merged, this should have been done in the same PR - apologises for that	9 years ago
Tom Harvey	25c3a879db	Adding `azurerm` to the list of supported backends (#16531) ... Fixes #16530	9 years ago
Martin Atkins	bcc5dffea2	provider/terraform: import terraform provider back into core	9 years ago
Martin Atkins	a3ced1a367	provider/terraform: reorganize for merge into core ... The "terraform" provider was previously split out into its own repository, but that turned out to be a mistake due to how tightly it depends on aspects of Terraform Core. Here we prepare to bring it back into the core repository by reorganizing the directory layout to conform with what's expected there.	9 years ago
Martin Atkins	3da5fefdc1	command: Allow TF_DATA_DIR env var to override data directory ... This allows the user to customize the location where Terraform stores the files normally placed in the ".terraform" subdirectory, if e.g. the current working directory is not writable.	9 years ago
James Bardin	229c70cabe	Merge pull request #16296 from stack72/manta-backend ... Migrate Manta Remote state to be a backend	9 years ago
Benjamin Farley	d6abdd14e7	website: correction of chunklist interpolation function example	9 years ago
Martin Atkins	4fa2b8c519	website: updated docs for the module registry protocol ... Now includes more complete information on usage of private registries and updates the module registry API documentation to include the new version-enumeration endpoint along with describing Terraform's discovery protocol.	9 years ago
Martin Atkins	91a4af9c8a	website: rewrite modules usage documentation for new features ... The modules mechanism has changed quite a bit for version 0.11 and so although simple usage remains broadly compatible there are some significant changes in the behavior of more complex modules. Since large parts of this were rewritten anyway, I also took the opportunity to do some copy-editing to make the prose on this page more consistent with our usual editorial voice and to wrap the long lines.	9 years ago
Martin Atkins	400038eda4	command: "terraform apply" uses interactive confirmation by default ... In the 0.10 release we added an opt-in mode where Terraform would prompt interactively for confirmation during apply. We made this opt-in to give those who wrap Terraform in automation some time to update their scripts to explicitly opt out of this behavior where appropriate. Here we switch the default so that a "terraform apply" with no arguments will -- if it computes a non-empty diff -- display the diff and wait for the user to type "yes" in similar vein to the "terraform destroy" command. This makes the commonly-used "terraform apply" a safe workflow for interactive use, so "terraform plan" is now mainly for use in automation where a separate planning step is used. The apply command remains non-interactive when given an explicit plan file. The previous behavior -- though not recommended -- can be obtained by explicitly setting the -auto-approve option on the apply command line, and indeed that is how all of the tests are updated here so that they can continue to run non-interactively.	9 years ago
stack72	1fd0f803e4	Migrate Manta Remote state to be a backend ... This PR changes manta from being a legacy remote state client to a new backend type. This also includes creating a simple lock within manta This PR also unifies the way the triton client is configured (the schema) and also uses the same env vars to set the backend up It is important to note that if the remote state path does not exist, then the backend will create that path. This means the user doesn't need to fall into a chicken and egg situation of creating the directory in advance before interacting with it	9 years ago
Greg Oliver	b5d3559d2d	website: refine the description of the azurerm backend	9 years ago
Florian Forster	927085289d	backend/remote-state/gcs: Implement the "region" config option. ... This allows to select the region in which a bucket is created. This copies behavior from the Google Cloud provider.	9 years ago
Florian Forster	9583d0945c	backend/remote-state/gcs: Add support for the GOOGLE_PROJECT environment variable. ... This copies behavior from the Google Cloud provider.	9 years ago
Florian Forster	52e6159219	backend/remote-state/gcs: Improve "bucket" and "credentials" documentation.	9 years ago
Florian Forster	df386d3133	backend/remote-state/gcs: Automatically create the bucket if needed. ... This resurrects the previously documented but unused "project" option. This option is required to create buckets (so they are associated with the right cloud project) but not to access the buckets later on (because their names are globally unique).	9 years ago