terraform

Commit Graph

Author	SHA1	Message	Date
Alisdair McDiarmid	aa8c73cd18	website: Credentials helper response for no creds For a credentials helper plugin to be useful with Terraform 0.13+, we need to cope with the case of having no credentials for a host without this being an error. This is to allow the public Terraform Registry to be accessed without supplying a token. The way to implement this is to respond to queries for credentials for a host which has no credentials stored with an empty object and a success exit code. This contradicts the previous documentation, which calls for an error response in this case.	6 years ago
Martin Atkins	2bd2a9a923	internal/getproviders: HTTPMirrorSource implementation We previously had this just stubbed out because it was a stretch goal for the v0.13.0 release and it ultimately didn't make it in. Here we fill out the existing stub -- with a minor change to its interface so it can access credentials -- with a client implementation that is compatible with the directory structure produced by the "terraform providers mirror" subcommand, were the result to be published on a static file server.	6 years ago
Nick Fagerlund	2ffb71bcee	website: Fix several broken links (#25808 )	6 years ago
Nick Fagerlund	0e5651560b	Website: 0.13 docs edits, mostly around provider requirements (#25686 ) * Make sidebar nav in language docs more intuitive * Minor display fixes for registry docs * Explain providers in the registry in the providers index * Revise a bunch of language docs around provider reqs This is mostly an effort to smooth out some of the explanations, make sure things are presented in a helpful order, make sure terminology lines up, draw connections between related concepts, make default behavior more apparent, and the like. It shouldn't include very much new information, but there might be one or two things that came out of a conversation somewhere. Co-authored-by: Judith Malnick <judith@hashicorp.com>	6 years ago
Pam Selle	9cf5a18532	Merge pull request #25238 from HadrienPatte/fix-json-output-format-docs Fix JSON output format documentation	6 years ago
Nick Fagerlund	b1eb9dcfcf	website: Configuration Language navigation refactoring The "Configuration Language" section was becoming rather unweildy, both by having a lot of pages and by some of the pages being quite large in themselves. This is a first step towards breaking things up a little more, starting with two changes: - The "Configuration Language" navigation is now split into two sub-headings "Configuration Blocks" and "Syntax". - Some of the information about sub-blocks of the "terraform" block are now given their own pages, because their content is quite complex in itself. - "Version Constraints" is now a page in its own right, rather than this content being duplicated in slightly different forms across multiple contexts that make use of user-specified version constraints.	6 years ago
Hadrien Patte	4dea1bb5a0	Fix JSON output format documentation	6 years ago
Martin Atkins	80a4bfbf27	website: New navigation items for the module and provider registry specs	6 years ago
Martin Atkins	63639defe9	website: Separate docs for the module registry protocol We previously had the module registry protocol documented only as an undefined subset of the full API of the official registry implementation. However, the vast majority of endpoints documented in the official API docs are not needed for a headless third-party module registry that only intends to make modules available to Terraform CLI. To make this clearer to potential third-party implementors, and also for consistency with how the provider registry protocol is now documented, here we create a new page to describe the subset required for all registries, and then explain in the docs for the offical API that potential third-party implementors should refer to the new page instead. The longer page describing the full API of the official implementations remains for those who wish to write clients for that API, because it is part of the API surface area for Terraform Cloud and Terraform Enterprise. I also took this opportunity to address the fact that module addresses don't really contain "provider names" at all, but rather than the fourth field in the address is _conventionally_ an official provider name but can really be any string that serves to differentiate multiple implementations of the same abstraction. The new docs therefore refer to this field as "system" rather than "provider".	6 years ago
Martin Atkins	deb8257fa5	website: Specification for the provider registry protocol	6 years ago
Pam Selle	146644a848	update addressing section	6 years ago
Pam Selle	65c4ba9c85	First docs for count/for_each on modules	6 years ago
Paddy	e6592dc710	Add support for provider metadata to modules. (#22583 ) Implement a new provider_meta block in the terraform block of modules, allowing provider-keyed metadata to be communicated from HCL to provider binaries. Bundled in this change for minimal protocol version bumping is the addition of markdown support for attribute descriptions and the ability to indicate when an attribute is deprecated, so this information can be shown in the schema dump. Co-authored-by: Paul Tyng <paul@paultyng.net>	6 years ago
Martin Atkins	778f1ab138	website: Documentation for the "terraform login" command (#22727 ) Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>	6 years ago
Brian Flad	cea149340c	docs/internal/resource-addressing: Omit for_each full splat example for now	7 years ago
Brian Flad	720b062d55	Apply suggestions from code review Co-Authored-By: Nick Fagerlund <nick@hashicorp.com>	7 years ago
Brian Flad	3ad05e50a4	docs/internal/resource-addressing: Add for_each information	7 years ago
Martin Atkins	04f3766fd9	website: Indicate v0.12-only content We have released the v0.12-oriented content to the website early in order to support the beta process, but in some places we neglected to explicitly mark features or content as being v0.12-only. Here we add explicit markers to the main cases we've seen where readers have reported confusion, along with some other tweaks in similar vein.	7 years ago
Nick Fagerlund	79c2fd2f3a	website: rename expressions-representation to block-expressions-representation	7 years ago
Kristin Laemmert	2aef47d01d	website: clarify format_version	7 years ago
Nick Fagerlund	3c42508700	Apply suggestions from code review Co-Authored-By: mildwonkey <mildwonkey@users.noreply.github.com>	7 years ago
Nick Fagerlund	883d587734	website: ACTUALLY fix indentation issues in config rep There was an issue with some hardtabs, I think.	7 years ago
Nick Fagerlund	4a19b53b55	website: Fix confusing indentation issues in configuration representation	7 years ago
Nick Fagerlund	92e609c98b	website: Revise json format doc	7 years ago
Nick Fagerlund	c2979e7278	website: fix JSON typo (resources is array of objects)	7 years ago
Nick Fagerlund	ff47cab8c7	website: Fix JSON typo (child_modules is array)	7 years ago
Nick Fagerlund	f6c5e33c00	website: fix highlighting and line breaks	7 years ago
Kristin Laemmert	a43004e382	website/docs: add detailed documentation for the json serialization of terraform plan	7 years ago
Chris Doherty	71c79522c6	website: Add docs/internals/archiving.html to describe the archiving process. (#18831 ) Add docs/internals/archiving.html to describe the archiving process.	8 years ago
Brian Flad	9b295e2bc7	docs/internal: Fix sidebar navigation for Remote Service Discovery page	8 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.	8 years ago
Martin Atkins	93651450b1	website: don't talk about graphs in the Getting Started guide Previously we just assumed the reader was familiar with the idea of a graph but didn't explain it. Since graphs are an implementation detail of Terraform, rather than essential information needed for new users, this revises the introduction text to talk only about _dependencies_, which we assume the user is familiar with as a more practical concept. Additionally, Paul Hinze did a great talk on how Terraform uses graphs at HashiConf 2016 which is good additional content for our existing "Graph Internals" page, which includes a concise explanation of the basics of graph theory.	9 years ago
Martin Atkins	7ed70bb00e	website: new filesystem layout for core/provider split This repo now contains only the core docs, with other content moving elsewhere.	9 years ago

33 Commits (6440c839474f052d8997bb5cec19c2743e5108e6)