27100 Commits (76ffe8aa7db2e8fcb5ea063067c638ed7bbbb075)

 

All Branches   

Search

Author	SHA1	Message	Date
r0bnet	76ffe8aa7d	lang/funcs: Functions for encoding text in specific character encodings	6 years ago
Alisdair McDiarmid	6d2f7f3f82	Merge pull request #26650 from hashicorp/alisdair/ignore-changes-sensitive-014 ... terraform: Fix sensitive values in ignore changes	6 years ago
Martin Atkins	660ede3231	replacefile: don't create the temporary file in TMPDIR ... ioutil.TempFile has a special case where an empty string for its dir argument is interpreted as a request to automatically look up the system temporary directory, which is commonly /tmp . We don't want that behavior here because we're specifically trying to create the temporary file in the same directory as the file we're hoping to replace. If the file gets created in /tmp then it might be on a different device and thus the later atomic rename won't work. Instead, we'll add our own special case to explicitly use "." when the given filename is in the current working directory. That overrides the special automatic behavior of ioutil.TempFile and thus forces the behavior we need. This hadn't previously mattered for earlier callers of this code because they were creating files in subdirectories, but this codepath was failing for the dependency lock file due to it always being created directly in the current working directory. Unfortunately since this is a picky implementation detail I couldn't find a good way to write a unit test for it without considerable refactoring. Instead, I verified manually that the temporary filename wasn't in /tmp on my Linux system, and hope that the comment inline will explain this situation well enough to avoid an accidental regression in future maintenence.	6 years ago
Alisdair McDiarmid	f07b4dd175	Update CHANGELOG.md	6 years ago
Alisdair McDiarmid	d28568e565	terraform: Fix sensitive values in ignore changes ... Because ignore_changes configuration can refer to resource arguments which are assigned sensitive values, we need to unmark the resource object before processing.	6 years ago
Pam Selle	8bf70c2cf6	Merge pull request #26649 from hashicorp/pselle/0.14-codecov ... [build][0.14] only run codecov on main branch	6 years ago
Pam Selle	c4911b9230	Only run codecov on master	6 years ago
Pam Selle	25f14c681e	Merge pull request #26646 from hashicorp/pselle/docs-0.14 ... [0.14 cherry pick] 0.14 guide updates	6 years ago
Pam Selle	a5b70e972a	Add note to upgrade guide about provider sensitivity (#26643) ... * Add note to upgrade guide about provider sensitivity Now that sensitivity follows attributes providers mark as sensitive, add this note to the upgrade guide. Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>	6 years ago
James Bardin	fff53cae9a	update CHANGELOG.md	6 years ago
James Bardin	527f3e654c	Merge pull request #26641 from hashicorp/jbardin/backport-26638 ... 0.14 backport 26638	6 years ago
James Bardin	060f8acc08	compare empty strings as null in sets ... The Legacy SDK cannot handle missing strings from objects in sets, and will insert an empty string when planning the missing value. This subverts the `couldHaveUnknownBlockPlaceholder` check, and causes errors when `dynamic` is used with NestingSet blocks. We don't have a separate codepath to handle the internals of AssertObjectCompatible differently for the legacy SDK, but we can treat empty strings as null strings within set objects to avoid the failed assertions.	6 years ago
Pam Selle	9ef9d3e952	Merge pull request #26635 from hashicorp/pselle/sensitivity-providers ... [0.14 port] Mark attributes providers mark as sensitive	6 years ago
Alisdair McDiarmid	a18415686b	Merge pull request #26630 from hashicorp/alisdair/sensitive-values-provisioners-014 ... Fixes for sensitive values used as input to provisioners	6 years ago
Pam Selle	394e60608c	Allocate new copies of paths to avoid append drama ... Create new copies of the Path to avoid possible append related dramas. Also add a test to cover nested block within blocks	6 years ago
Alisdair McDiarmid	2b485cd428	website: Sensitive values in provisioner config	6 years ago
Alisdair McDiarmid	47f8ed4cd6	terraform: Hide maybe-sensitive provisioner output ... If the provisioner configuration includes sensitive values, it's a reasonable assumption that we should suppress its log output. Obvious examples where this makes sense include echoing a secret to a file using local-exec or remote-exec. This commit adds tests for both logging output from provisioners with non-sensitive configuration, and suppressing logs for provisioners with sensitive values in configuration. Note that we do not suppress logs if connection info contains sensitive information, as provisioners should not be logging connection information under any circumstances.	6 years ago
Alisdair McDiarmid	c5cc7cdd62	terraform: Unmark provisioner arguments ... If provisioner configuration or connection info includes sensitive values, we need to unmark them before calling the provisioner. Failing to do so causes serialization to error. Unlike resources, we do not need to capture marked paths here, so we just discard the marks.	6 years ago
James Bardin	f4b686b5f3	Merge pull request #26614 from hashicorp/jbardin/0.14-26606 ... 0.14 backport of #26606	6 years ago
Martin Atkins	afe1e4e9a1	command/cliconfig: Allow development overrides for providers ... For normal provider installation we want to associate each provider with a selected version number and find a suitable package for that version that conforms to the official hashes for that release. Those requirements are very onerous for a provider developer currently testing a not-yet-released build, though. To allow for that case this new CLI configuration feature allows overriding specific providers to refer to give local filesystem directories. Any provider overridden in this way is not subject to the usual restrictions about selected versions or checksum conformance, and activating an override won't cause any changes to the selections recorded in the lock file because it's intended to be a temporary setting for one developer only. This is, in a sense, a spiritual successor of an old capability we had to override specific plugins in the CLI configuration file. There were some vestiges of that left in the main package and CLI config package but nothing has actually been honoring them for several versions now and so this commit removes them to avoid confusion with the new mechanism.	6 years ago
James Bardin	a8429b027c	handle non-null, but empty NestingMap in a set	6 years ago
James Bardin	2687cd635f	refactor ifs to reduce indentation	6 years ago
James Bardin	abe82509fb	take dynamic types into account when comparing set ... If a NestingList or NestingMap contains a dynamic type, they must be handled as a cty.Tuple and cty.Object respectively, because the elements may not have precisely matching types.	6 years ago
Alexander Ovechkin	7373e620e3	added empty list test case	6 years ago
Alexander Ovechkin	872803e39a	Converting ListVal to ListVal instead of TupleVal in setElementCompareValue	6 years ago
Petros Kolyvas	9835a7f3db	Update 0-14.html.markdown (#26591)	6 years ago
Pam Selle	a9823515ec	Update context apply test	6 years ago
Pam Selle	a1a46425bd	Set and single test coverage	6 years ago
Pam Selle	a5c5d2c28c	Cover NestingMap case	6 years ago
Pam Selle	f790332bff	NestingList support tested	6 years ago
Pam Selle	10cffc477d	Basic test for GetResource, plus sensitivity	6 years ago
hashicorp-ci	33cc81e65e	Cleanup after v0.14.0-beta1 release	6 years ago
hashicorp-ci	0671bc7eab	Release v0.14.0-beta1	6 years ago
James Bardin	1ecd86d08e	Merge pull request #26155 from hashicorp/unused-env-var ... Remove unused env var TF_SKIP_PROVIDER_VERIFY	6 years ago
James Bardin	ffbdd72196	Merge pull request #26487 from hashicorp/jbardin/shell-escape ... update taint command example	6 years ago
Pam Selle	ee9ec8a193	Reordering so attributes are first (understandability)	6 years ago
Pam Selle	e44e03b283	If our block doesn't contain any sensitive attrs, skip recursing into it	6 years ago
Pam Selle	f60ae7ac08	Mark sensitive attributes in blocks ... This implements marking sensitive attributes within blocks when referenced by adding recursive calls to get more paths from blocks' attributes	6 years ago
James Bardin	014fb898d5	Merge pull request #26589 from hashicorp/jbardin/vet-fixes ... Fixes for go vet	6 years ago
Pam Selle	5e2905d222	Mark attributes providers mark as sensitive ... This updates GetResource so that the value returned has marks where the provider's schema has marked an attribute as sensitive	6 years ago
James Bardin	98d01615f6	unreachable	6 years ago
James Bardin	c61a893590	unused tests ... these are no longer relevant	6 years ago
James Bardin	5e9425b562	unreachable	6 years ago
James Bardin	b8df47c9ac	add struct field names	6 years ago
Alisdair McDiarmid	b1500db6b9	Merge pull request #26585 from hashicorp/alisdair/update-hcl-cty ... Update hcl and go-cty dependencies	6 years ago
James Bardin	657dd33008	Merge pull request #26557 from remilapeyre/skip-ddl-commands ... Add skip_table_creation and skip_index_creation options to the pg backend	6 years ago
James Bardin	08abf5d561	Merge pull request #26577 from hashicorp/jbardin/decoder-spec ... Memoize Block.DecoderSpec	6 years ago
James Bardin	e27ecba6e4	extended cache comments	6 years ago
Petros Kolyvas	dc48450e79	Provisioner contribution guide updates (#26538) ... An update on the deprecated state of vendor provisioners for our contribution guide.	6 years ago
Martin Atkins	0009768c7f	internal/depsfile: Update the dependency lock file atomically ... In this case, "atomic" means that there will be no situation where the file contains only part of the newContent data, and therefore other software monitoring the file for changes (using a mechanism like inotify) won't encounter a truncated file. It does _not_ mean that there can't be existing filehandles open against the old version of the file. On Windows systems the write will fail in that case, but on Unix systems the write will typically succeed but leave the existing filehandles still pointing at the old version of the file. They'll need to reopen the file in order to see the new content.	6 years ago