28484 Commits (69ebfd6f037f8d51709770cc36d266bb86cf950d)

 

All Branches   

Search

Author	SHA1	Message	Date
Laura Pacilio	d3b9d5cdda	Update website/README.md ... Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Laura Pacilio	b3736334f7	Update website/README.md ... Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Laura Pacilio	52e2094726	Update website/README.md ... Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Laura Pacilio	f2d89464ef	Revise grouping in steps	5 years ago
Laura Pacilio	10ccf2bd7f	Add more context to run instructions	5 years ago
Laura Pacilio	0fc32e5858	Fix indentation	5 years ago
Laura Pacilio	03e6f0d385	Update formatting for terminal commands	5 years ago
Laura Pacilio	c2b492a814	Add initial run local instructions to readme	5 years ago
Laura Pacilio	dfc12a6a9e	Merge pull request #29051 from hashicorp/add-page-metadata ... Add page metadata	5 years ago
Martin Atkins	6b8e103d6a	configs: Include "moved" blocks when merging multiple files into a module ... An earlier commit added logic to decode "moved" blocks and do static validation of them. Here we now include that result also in modules produced from those files, which we can then use in Terraform Core to actually implement the moves. This also places the feature behind an active experiment keyword called config_driven_move. For now activating this doesn't actually achieve anything except let you include moved blocks that Terraform will summarily ignore, but we'll expand the scope of this in later commits to eventually reach the point where it's really usable.	5 years ago
Martin Atkins	d92b5e5f5e	configs: valid-modules test ignores experimental features warning ... A common source of churn when we're running experiments is that a module that would otherwise be valid ends up generating a warning merely because the experiment is active. That means we end up needing to shuffle the test files around if the feature ultimately graduates to stable. To reduce that churn in simple cases, we'll make an exception to disregard the "Experiment is active" warning for any experiment that a module has intentionally opted into, because those warnings are always expected and not a cause for concern. It's still possible to test those warnings explicitly using the testdata/warning-files directory, if needed.	5 years ago
Martin Atkins	708003b035	configs: For Moved blocks, use addrs.MoveEndpoint instead of addrs.Target ... Although addrs.Target can in principle capture the information we need to represent move endpoints, it's semantically confusing because addrs.Targetable uses addrs.Abs... types which are typically for absolute addresses, but we were using them for relative addresses here. We now have specialized address types for representing moves and probably other things which have similar requirements later on. These types largely communicate the same information in the end, but aim to do so in a way that's explicit about which addresses are relative and which are absolute, to make it less likely that we'd inadvertently misuse these addresses.	5 years ago
Martin Atkins	4cbe6cabfc	addrs: AbsMoveable, ConfigMoveable, and MoveableEndpoint ... These three types represent the three different address representations we need to represent different stages of analysis for "moved" blocks in the configuration. The goal here is to encapsulate all of the static address wrangling inside these types so that users of these types elsewhere would have to work pretty hard to use them incorrectly. In particular, the MovableEndpoint type intentionally fully encapsulates the weird relative addresses we use in configuration so that code elsewhere in Terraform can never end up holding an address of a type that suggests absolute when it's actually relative. That situation only occurs in the internals of MoveableEndpoint where we use not-really-absolute AbsMoveable address types to represent the not-yet-resolved relative addresses. This only takes care of the static address wrangling. There's lots of other rules for what makes a "moved" block valid which will need to be checked elsewhere because they require more context than just the content of the address itself.	5 years ago
Martin Atkins	3212f6f367	addrs: AbsModuleCall type ... Our documentation for ModuleCall originally asserted that we didn't need AbsModuleCall because ModuleInstance captured the same information, but when we added count and for_each for modules we introduced ModuleCallInstance to represent a reference to an instance of a local module call, and now _that_ is the type whose absolute equivalent is ModuleInstance. We previously had no absolute representation of the call itself, without any particular instance. That's what AbsModuleCall now represents, allowing us to be explicit about when we're talking about the module block vs. instances it declares, which is the same distinction represented by AbsResource vs. AbsResourceInstance. Just like with AbsResource and AbsResourceInstance though, there is syntactic ambiguity between a no-key call instance and a whole module call, and so some codepaths might accept both to start and then use other context to dynamically choose a particular interpretation, in which case this distinction becomes meaningful in representing the result of that decision.	5 years ago
Martin Atkins	ab350289ab	addrs: Rename AbsModuleCallOutput to ModuleCallInstanceOutput ... The previous name didn't fit with the naming scheme for addrs types: The "Abs" prefix typically means that it's an addrs.ModuleInstance combined with whatever type name appears after "Abs", but this is instead a ModuleCallOutput combined with an InstanceKey, albeit structured the other way around for convenience, and so the expected name for this would be the suffix "Instance". We don't have an "Abs" type corresponding with this one because it would represent no additional information than AbsOutputValue.	5 years ago
Laura Pacilio	e6f1255869	Update vs Cloudformation description	5 years ago
Laura Pacilio	ab9b9a445f	Update vs pages to address PR comments	5 years ago
Laura Pacilio	09c79994f5	Update use cases page for PR comments	5 years ago
Laura Pacilio	04385bb9fc	Update website/intro/use-cases.html.markdown ... Co-authored-by: Judith Malnick <judith.patudith@gmail.com>	5 years ago
Laura Pacilio	a9e09a3ed9	Edit copy to address PR comments	5 years ago
Sam Salisbury	2fdf898680	Merge pull request #29064 from hashicorp/darwin-arm64 ... Build darwin/arm64 (RELENG-650)	5 years ago
hc-github-team-tf-core	f2d1817a57	Cleanup after v1.1.0-alpha20210630 release	5 years ago
hc-github-team-tf-core	e291ace3eb	Release v1.1.0-alpha20210630	5 years ago
Laura Pacilio	a8d949a590	Add compatibility promises to sidebar toc	5 years ago
Laura Pacilio	577c3653f2	Merge pull request #28983 from KurtLehnardt/patch-1 ... fixed typo	5 years ago
Laura Pacilio	a7e24c384b	Merge pull request #28842 from iaoiui/patch-1 ... remove extra "be"	5 years ago
Laura Pacilio	f9ec36383d	Merge pull request #29011 from vlad-ro/patch-1 ... Add back missing closing quote character	5 years ago
Laura Pacilio	4f12b8d917	Merge pull request #28863 from stensonb/patch-1 ... typo	5 years ago
Laura Pacilio	f200c5d0ef	Merge pull request #29032 from hashicorp/izaaklauer/typo ... Small comment typo	5 years ago
Laura Pacilio	de97a03528	Merge pull request #28908 from kondr57/patch-1 ... fix typo	5 years ago
Sam Salisbury	e17abccf2e	ci: add darwin/arm64 to workflow	5 years ago
Sam Salisbury	2337334b1f	ci: add darwin/arm64 build	5 years ago
Kristin Laemmert	35c19d7c9f	command/jsonstate: remove redundant remarking of resource instance (#29049) ... * command/jsonstate: remove redundant remarking of resource instance ResourceInstanceObjectSrc.Decode already handles marking values with any marks stored in ri.Current.AttrSensitivePaths, so re-applying those marks is not necessary. We've gotten reports of panics coming from this line of code, though I have yet to reproduce the panic in a test. * Implement test to reproduce panic on #29042 Co-authored-by: David Alger <davidmalger@gmail.com>	5 years ago
Laura Pacilio	a2cab95dac	Update copy for active voice and concision	5 years ago
Laura Pacilio	740343cfd2	Update website/intro/use-cases.html.markdown ... Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Laura Pacilio	2cb8bbaacd	Update website/intro/use-cases.html.markdown ... Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Laura Pacilio	16bea6a949	Update website/intro/use-cases.html.markdown ... Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Laura Pacilio	7cb7d641b7	Remove top header and add provider language	5 years ago
Laura Pacilio	46708ea4bc	Update website/intro/vs/chef-puppet.html.markdown ... Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Laura Pacilio	f526e6eadc	Update page description metadata	5 years ago
Laura Pacilio	5e89ac590e	Update page description metadata	5 years ago
Laura Pacilio	908ceec8c1	Update page description metadata	5 years ago
Laura Pacilio	fc772aec86	Update page content for clarity, concision, and flow	5 years ago
Laura Pacilio	2f67c78821	Update page description metadata	5 years ago
Laura Pacilio	4111b1298d	Update page description metadata	5 years ago
Martin Atkins	512e4e7f13	Update CHANGELOG.md	5 years ago
Martin Atkins	70bc432f85	command/views/json: Never generate invalid diagnostic snippet offsets ... Because our snippet generator is trying to select whole lines to include in the snippet, it has some edge cases for odd situations where the relevant source range starts or ends directly at a newline, which were previously causing this logic to return out-of-bounds offsets into the code snippet string. Although arguably it'd be better for the original diagnostics to report more reasonable source ranges, it's better for us to report a slightly-inaccurate snippet than to crash altogether, and so we'll extend our existing range checks to check both bounds of the string and thus avoid downstreams having to deal with out-of-bounds indices. For completeness here I also added some similar logic to the human-oriented diagnostic formatter, which consumes the result of the JSON diagnostic builder. That's not really needed with the additional checks in the JSON diagnostic builder, but it's nice to reinforce that this code can't panic (in this way, at least) even if its input isn't valid.	5 years ago
Laura Pacilio	5344ba0fa5	Update page description metadata	5 years ago
Laura Pacilio	0ab2012d77	Update page description metadata	5 years ago
Laura Pacilio	e92f030662	Make get started bullet more concise	5 years ago