2075 Commits (a574e95dcde2d3bbb399b025f515ccd062abeeca)

Author	SHA1	Message	Date
Laura Pacilio	a574e95dcd	Merge pull request #31834 from fungusakafungus/patch-1 ... Looks like a copy-paste error	3 years ago
Brandon Croft	be5984d664	Merge pull request #32004 from hashicorp/brandonc/nested_attr_sensitive ... fix: don't reveal nested attributes with sensitive schema	3 years ago
Laura Pacilio	ec42b167d7	fix broken links	3 years ago
Tom Bamford	ff68c8d129	Merge pull request #31966 from kschu91/feature/azure-generic-oidc ... backend/azurerm: add support for generic OIDC authentication	3 years ago
Liam Nesteroff	5957d2657a	Update GCS backend docs for TF >=0.12 (#32065) ... * Update gcs.mdx Updated GCS remote backend to include the >=0.12 remote backend data source formatting (incl .output before output name) * Update gcs.mdx removed old data source example * Update gcs.mdx updated to local_file and output->outputs * Update gcs.mdx removed "outputs" from the pre 0.12 ref	3 years ago
Brandon Croft	f5de1099ff	Merge pull request #31768 from hashicorp/brandonc/providers-estimate ... Update the # public providers estimate in the Terraform Intro	3 years ago
Brandon Croft	43ade2b6a1	Update website/docs/intro/index.mdx	3 years ago
Laura Pacilio	2aaaf28b75	Merge pull request #31830 from sdinay/patch-2 ... Update links to deprecated aws_s3_bucket_object to aws_s3_object	3 years ago
Laura Pacilio	20b3e8e5a1	Merge pull request #31792 from mferraroni/doc-s3-fix ... Modifies permissions needed to use s3 with dynamoDb locks	3 years ago
Laura Pacilio	fbfe5b5a87	Merge pull request #31508 from wzyboy/docs/unknwon-value ... docs: fix typo regarding unknown values	3 years ago
Laura Pacilio	c3c6f8327f	Merge pull request #31149 from hashicorp/docs-for-each-list-toset ... fix(docs): change set to list when recommending using toset()	3 years ago
Brandon Croft	bd744ad4e9	Unify all sensitive value plan output as "(sensitive value)" ... Previously, there was mixed usage of "(sensitive)" and "(sensitive value)" and even though it was more common to see "(sensitive)", the thought is that it's a value we are hiding rather than describing something already shown.	3 years ago
Kevin Wang	03e262a70b	chore: rewrite internal redirects (#32038)	3 years ago
Laura Pacilio	58ad930f2d	Revert "more content updates for flow" ... This reverts commit 84edd84471.	3 years ago
Laura Pacilio	cb975a5fff	Revert "Remove future-facing statements" ... This reverts commit 0a7e221a49.	3 years ago
Laura Pacilio	84edd84471	more content updates for flow	3 years ago
Laura Pacilio	0a7e221a49	Remove future-facing statements	3 years ago
Tom Bamford	0dac887547	Docs for azurerm generic OIDC	3 years ago
Sarah French	89ef27d3b4	Add Private Service Connect endpoint support to GCS backend (#31967) ... * Add support for `storage_custom_endpoint` in `gcs` backend * Add documentation for new `storage_custom_endpoint` endpoint * Empty commit to trigger Vercel deployment	3 years ago
Matthew Garrell	03bff99caa	Merge pull request #31954 from hashicorp/mg_no_code_prov_followup ... Adding mention of no-code to Creating Modules section of TF Language docs	3 years ago
Matthew Garrell	a50d8cfc11	Adding mention of no-code to Modules section of TF Language docs	3 years ago
Laura Pacilio	c8d8536160	Add callout to Continuous Validation	3 years ago
Laura Pacilio	8258070fd5	Update website/docs/language/state/backends.mdx	4 years ago
Laura Pacilio	97c628044a	Update website/docs/language/state/backends.mdx	4 years ago
Laura Pacilio	bed5650e2f	Update backends.mdx	4 years ago
Sarah French	d43ec0f30f	Add customer-managed encryption key (KMS) support to GCS backend (#31786) ... * Add ability to use customer-managed KMS key to encrypt state, add acceptance tests * Change test names for different encrpytion methods * Commit files updated by `go mod tidy` * Add guard against missing ENVs to `setupKmsKey` func * Update KMS setup function to get credentials from ENVs * Update tests to not include zero-values in config This means that default values are supplied later by TF instead of supplied as config from the user This also avoids issues related to making field conflicts explicit with `ConflictsWith` * Make `encryption_key` & `kms_encryption_key` conflicting fields Removing the Default from `encryption_key` does not appear to be a breaking change when tested manually * Add ability to set `kms_encryption_key` via ENV * Refactor `encryption_key` to use `DefaultFunc` to access ENV, if set * Remove comments * Update `gcs` backend docs & descriptions in schema * Update `gcs` backend docs to include information on encryption methods * Apply technical writing suggestions from code review Co-authored-by: Matthew Garrell <69917312+mgarrell777@users.noreply.github.com> * Update documentation to remove passive voice * Change use of context in tests, add inline comment, update logs * Remove use of `ReadPathOrContents` for new field Co-authored-by: Matthew Garrell <69917312+mgarrell777@users.noreply.github.com>	4 years ago
Craig Wright	e7fb895c46	Merge pull request #31876 from zisom-hc/patch-1 ... Update custom-conditions.mdx	4 years ago
Martin Atkins	f260ed1177	website: Remove warning that yamlencode is experimental ... We originally included this warning because the go-cty-yaml module wasn't yet stable and it was also not extensively tested so it wasn't yet clear if its behavior would need to change in some less common cases we hadn't tested so far. However, go-cty-yaml had its v1.0.0 release some time ago and is now committed to preserving its current Marshal output unless it is found to be non-compliant with the YAML 1.2 specification. This doc change means that Terraform's yamlencode is now adopting a similar posture: - The exact style details produced by the function for a particular input are now frozen. It'll change only if we find that the function is producing output that isn't valid per the YAML spec. - If someone finds a YAML parser that cannot parse what yamlencode produces but what it produces is valid per the YAML 1.2 spec, we'll expect the parser to be corrected to better support the spec rather than changing the yamlencode output. There may be pragmatic exceptions if we encounter a situation we cannot anticipate yet, but the above will be our general rule. This is really just a specialization of the spirit of the v1.x Compatibility Promises, tailored specifically to this function.	4 years ago
zisom-hc	d08fcd63db	Update custom-conditions.mdx ... Made a change to code example within the *Preconditions and Postconditions* section so that it technically makes sense; prior it was missing the data resource that was being called within the precondition lifecycle event on line 135, and the aws_instance resource was not utilizing the ami being provided by the data source in line 129, so i changed that as well.	4 years ago
Laura Pacilio	a8ea377e7f	Merge pull request #31849 from hashicorp/workspaces-confusion-fixes ... Update workspace documentation	4 years ago
Laura Pacilio	0471c80ebe	Update website/docs/language/state/workspaces.mdx	4 years ago
Laura Pacilio	2ea3765fa6	Update website/docs/language/state/workspaces.mdx	4 years ago
Laura Pacilio	6753fb5476	Update website/docs/language/state/workspaces.mdx	4 years ago
Laura Pacilio	776c25777d	Update website/docs/language/state/workspaces.mdx	4 years ago
Laura Pacilio	94eed2c45b	Incorporate PR feedback	4 years ago
Matthew Garrell	1e6f091976	Merge pull request #31598 from bobsut/patch-1 ... insert missing infinitive particle	4 years ago
Laura Pacilio	f7bf19525e	Move TFC workspaces section further down	4 years ago
Laura Pacilio	35a5e92687	language fix	4 years ago
Laura Pacilio	2fc8289cf1	More updates to workspaces in language	4 years ago
Laura Pacilio	6c34047efa	Update workspace documentation	4 years ago
koki-develop	d5df330696	fixed typo: startsswith -> startswith	4 years ago
Ilya Margolin	e4d5ffd8eb	Looks like a copy-paste error	4 years ago
Laura Pacilio	9582cc2d0f	Remove unnecessary version note	4 years ago
S Dinay	bbf60cdd65	Update links aws_s3_bucket_object to aws_s3_bucket ... The remote-state-data documentation page refers to the aws_s3_bucket_object resource and data which is deprecated. The documentation says to use aws_s3_object instead. This change updates the links for the S3 object solution for remote state.	4 years ago
Martynas Šateika	c726a25fcd	Update taint.mdx	4 years ago
Martin Atkins	65ad73fe03	website: Tombstone callout for the v1.3 removed backends ... We've removed the main documentation pages for the backends that are removed in Terraform v1.3, but we'll leave a small callout note so that the backend names are still reachable through our search index once the v1.3 docs are the active version. The primary goal here is to help folks who have inherited configurations using older versions of Terraform to learn about features they see in those configurations, so the main thing here is the link to the older release docs which include those. However, this is also a good opportunity to link to the upgrade guide content which describes some possible migration paths away from these removed backends.	4 years ago
Bryce Kalow	b54017ef83	website: content updates for developer (#31779) ... Co-authored-by: Matthew Garrell <69917312+mgarrell777@users.noreply.github.com> Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com> Co-authored-by: Kevin Wang <kwangsan@gmail.com> Co-authored-by: Judith Malnick <judith@hashicorp.com> Co-authored-by: Martin Atkins <mart@degeneration.co.uk> Co-authored-by: HashiBot <62622282+hashibot-web@users.noreply.github.com>	4 years ago
Matteo Ferraroni	0900b787f8	Modifies permissions needed to use s3 with dynamoDb locks	4 years ago
Laura Pacilio	ee61929a9c	update note on provisioners page	4 years ago
Laura Pacilio	a891119b61	Remove legacy provisioners from docs	4 years ago