terraform

Commit Graph

Author	SHA1	Message	Date
Kristin Laemmert	563f1436eb	various docs updates (#29018 ) * website/docs: add sensitivity warning to output documentation fixes #28005 * website/docs: add note about ** to fileset documentation closes #24220 * website/docs: add note that `dynamic` expressions aren't included in json config output closes #28346 * website: the provider installer isn't necessarily concurrency safe closes #28367	5 years ago
Kristin Laemmert	ac03d35997	jsonplan and jsonstate: include sensitive_values in state representations (#28889 ) * jsonplan and jsonstate: include sensitive_values in state representations A sensitive_values field has been added to the resource in state and planned values which is a map of all sensitive attributes with the values set to true. It wasn't entirely clear to me if the values in state would suffice, or if we also need to consult the schema - I believe that this is sufficient for state files written since v0.15, and if that's incorrect or insufficient, I'll add in the provider schema check as well. I also updated the documentation, and, since we've considered this before, bumped the FormatVersions for both jsonstate and jsonplan.	5 years ago
Alisdair McDiarmid	a5b7394f9a	command/jsonplan: Add replace_paths The set of paths which caused a resource update to require replacement has been stored in the plan since 0.15.0 (#28201). This commit adds a simple JSON representation of these paths, allowing consumers of this format to determine exactly which paths caused the resource to be replaced. This representation is intentionally more loosely encoded than the JSON state serialization of paths used for sensitive attributes. Instead of a path step being represented by an object with type and value, we use a more-JavaScripty heterogenous array of numbers and strings. Any practical consumer of this format will likely traverse an object tree using the index operator, which should work more easily with this format. It also allows easy prefix comparison for consumers which are tracking paths. While updating the documentation to include this new field, I noticed that some others were missing, so added them too.	5 years ago
Martin Atkins	b802237e03	plans: Track an optional extra "reason" for some planned actions Previously we were repeating some logic in the UI layer in order to recover relevant additional context about a change to report to a user. In order to help keep things consistent, and to have a clearer path for adding more such things in the future, here we capture this user-facing idea of an "action reason" within the plan model, and then use that directly in order to decide how to describe the change to the user. For the moment the "tainted" situation is the only one that gets a special message, matching what we had before, but we can expand on this in future in order to give better feedback about the other replace situations too. This also preemptively includes the "replacing by request" reason, which is currently not reachable but will be used in the near future as part of implementing the -replace=... plan command line option to allow forcing a particular object to be replaced. So far we don't have any special reasons for anything other than replacing, which makes sense because replacing is the only one that is in a sense a special case of another action (Update), but this could expand to other kinds of reasons in the future, such as explaining which of the few different reasons a data source read might be deferred until the apply step.	5 years ago
Nick Fagerlund	d1e8537b33	website: CLI: Update links to moved docs pages	5 years ago
Nick Fagerlund	7a8dd326c6	website: Language: Update links to moved pages	5 years ago
Nick Fagerlund	85d477aee9	website: Fix numerous links with redirects or broken anchors These links largely still go somewhere useful, but they have some kind of issue revealed by our new link checker: - Some of them point to a stale URL that redirects, and can be updated to the new destination. - Some of them point to anchors that don't exist (anymore?) in the destination. - Some of them end up redirecting unnecessarily due to how the server handles directory URLs without trailing slashes. Sorry, I know that's pointless, just, humor me for the time being so we can get our CI green. 😭 In a couple cases, I've added invisible anchors to destination pages, either to preserve an old habit or because the current anchors kind of suck due to being particularly long or meandering.	5 years ago
Hadrien Patte	4dea1bb5a0	Fix JSON output format documentation	6 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

18 Commits (277fe647b95e32b9ca0738cd20af09735954dfd8)