22031 Commits (08344a41598396919f9b00a28bb9ddac2ebf80c0)

 

All Branches   

Search

Author	SHA1	Message	Date
Martin Atkins	08344a4159	govendor fetch github.com/hashicorp/hcl2/... ... This is a general catchup of some developments in the HCL2 codebase, but in particular includes: - Recording expression and evalcontext as part of diagnostics, so that variable value information can be included alongside diagnostic snippets. - hcldec supports decoding blocks into tuple and object values as well as list and map values, which then allows cty.DynamicPseudoType nested attributes to work properly.	8 years ago
Martin Atkins	aa20c4085a	govendor fetch golang.org/x/sys/unix/... ... This new version defines some symbols that are required by the grpc library.	8 years ago
James Bardin	7d7c77ad13	Merge pull request #18686 from hashicorp/jbardin/plugins ... plugin mocks	8 years ago
Martin Atkins	e39842332c	providers: Resolver and Factory types ... These new types are adaptations of terraform.ProviderResolver and terraform.ResourceProviderFactory respectively. In a later commit we will update users of the old types to use these new types, possibly in a "gradual repair" sort of fashion by initially using type aliases, though that won't 100% solve the problem because the types themselves have changed in this move to return providers.Interface instead of terraform.ResourceProvider.	8 years ago
James Bardin	e2b7c6b920	add new provider and provisioner mocks ... MockProvider and MockProvisioner implement the new plugin interfaces, and are built following the patterns used by the legacy MockResourceProvider and MockResourceProvisioner	8 years ago
James Bardin	37864624d3	add Close method to the terraform provider ... Close is now part of the plugin interfaces, so needs to be implemented by the terraform provider.	8 years ago
James Bardin	afca7f98dd	add Close methods to the plugin interfaces ... Close was previously an optional interface, because it's only applicable on the client side but the types were shared accross all packages. Since all plugins will now implement Close, it no longer needs to be optional.	8 years ago
James Bardin	ebfd8d869a	Merge pull request #18685 from hashicorp/jbardin/plugins ... move conversion functions into separate package	8 years ago
James Bardin	a65f696bbb	move conversion functions into separate package ... Managing which function need to be shared between the terraform plugin and the helper plugin without creating cycles was becoming difficult. Move all functions related to converting between terraform and proto type into plugin/convert.	8 years ago
James Bardin	91863e3a60	schema version changed type	8 years ago
James Bardin	0544f82447	Merge pull request #18678 from hashicorp/jbardin/grpc-plugins ... new plugin shims	8 years ago
James Bardin	eb321a1174	update go-plugin with proto negotiation	8 years ago
Martin Atkins	ade3b4575e	terraform: Ugly huge change to weave in new State and Plan types ... Due to how often the state and plan types are referenced throughout Terraform, there isn't a great way to switch them out gradually. As a consequence, this huge commit gets us from the old world to a _compilable_ new world, but still has a large number of known test failures due to key functionality being stubbed out. The stubs here are for anything that interacts with providers, since we now need to do the follow-up work to similarly replace the old terraform.ResourceProvider interface with its replacement in the new "providers" package. That work, along with work to fix the remaining failing tests, will follow in subsequent commits. The aim here was to replace all references to terraform.State and its downstream types with states.State, terraform.Plan with plans.Plan, state.State with statemgr.State, and switch to the new implementations of the state and plan file formats. However, due to the number of times those types are used, this also ended up affecting numerous other parts of core such as terraform.Hook, the backend.Backend interface, and most of the CLI commands. Just as with 5861dbf3fc before, I apologize in advance to the person who inevitably just found this huge commit while spelunking through the commit history.	8 years ago
Martin Atkins	7ed152bbd8	states: Port stringer implementation from terraform.State ... Our existing core tests make extensive use of the string representation of a state for comparison purposes, because they were written before we began making use of helper packages like "cmp". To avoid the need to rewrite all of those tests and potentially break them, we will instead port that particular rendering as closely as possible but mark it with a comment sternly warning not to use it for anything new. We don't want to use this moving forward for a number of reasons, but most notably: - printing out whole before and after state representations makes it hard to find a subtle difference in outcome when a test fails, while "cmp" can provide us with a real diff. - this string serialization is constrained by the capabilities of Terraform prior to our new state models, and so it does not comprehensively represent all possibilities in the new world. - it will probably behave oddly/poorly when given states containing features that arrived after it was written, even though I made a best effort here to make it do something reasonable in situations I thought about.	8 years ago
Martin Atkins	1ce3392f63	states: separate types for encoded and decoded state objects ... The types here were originally written to allow us to defer decoding of object values until schemas are available, but it turns out that this was forcing us to defer decoding longer than necessary and potentially decode the same value multiple times. To avoid this, we create pairs of types to represent the encoded and decoded versions and methods for moving between them. These types are identical to one another apart from how the dynamic values are represented.	8 years ago
Martin Atkins	44a4e2efdb	plans: separate types for encoded and decoded changes ... The types here were originally written to allow us to defer decoding of object values until schemas are available, but it turns out that this was forcing us to defer decoding longer than necessary and potentially decode the same value multiple times. To avoid this, we create pairs of types to represent the encoded and decoded versions and methods for moving between them. These types are identical to one another apart from how the dynamic values are represented.	8 years ago
Martin Atkins	6a39759145	statemgr: Helper funcs RefreshAndRead and WriteAndPersist ... In practice these pairs of functions are often used together when working with a "full" statemgr, so these helper wrappers allow us to do that more conveniently. This also introduces a new interface statemgr.Storage, which represents a state manager that has all of the storage capabilities but does not necessarily support locking. In practice callers will usually just use statemgr.Full, but these more-specific interfaces allow us to reflect in APIs which subset of the statemgr functionality each function depends on.	8 years ago
James Bardin	de11eed345	serve the new version 5 grpc plugins ... Use the new go-plugin version negotiation to server th appropriate plugin type when the client requests protocol version 5.	8 years ago
James Bardin	37ab3798cc	update tests to match new test func signature	8 years ago
James Bardin	19fdd6430f	add grpc shims to helper/plugin ... Add shim functions to automatically wrap plugins in the new GRPC implementations.	8 years ago
Kristin Laemmert	d6b05285d1	Merge pull request #18625 from hashicorp/mildwonkey/pitr ... Terraform Providers in the Registry	8 years ago
Kristin Laemmert	831fb5c1f9	registry/response: rename Collection to ProviderVersionCollection for clarity	8 years ago
James Bardin	4d3742a90e	Merge pull request #18638 from hashicorp/jbardin/grpc-plugins ... grpc plugins	8 years ago
James Bardin	ebe9957dfa	vendor gomock	8 years ago
James Bardin	73944d80ec	remove old comment	8 years ago
Kristin Laemmert	c55f6aaf05	registry/client: added a specific error if the registry client does not ... support the requested service.	8 years ago
James Bardin	73fd5acbc2	helper/plugin package for grpc servers ... The new helper/plugin package contains the grpc servers for handling the new plugin protocol The GRPCProviderServer and GRPCProvisionerServer handle the grpc plugin protocol, and convert the requests to the legacy schema.Provider and schema.Provisioner methods.	8 years ago
James Bardin	42f50c3b8a	fix package provisioners package name	8 years ago
James Bardin	ea9aaefbcd	minor providers.Interface fixes ... Add a missing TerraformVersion field, and fix a TypeName field.	8 years ago
James Bardin	23dec00f8e	GRPCProvider and GRPCProvisioner clients ... Here we add the GRPCProvisioner and GRPCProvider which implement the core provisioners.Interface and providers.Interface, and translate betweeen the core types and the grpc protocol.	8 years ago
James Bardin	12c3e641e3	generate mocks for some of the grpc interfaces ... These will allow easier testing of the grpc endpoints in isolation. Mocks are generated for ProviderClient, ProvisionerClient, Provisioner_ProvisionResourceClient, and Provisioner_ProvisionResourceServer using `go generate`	8 years ago
James Bardin	d6dc738abb	grpc proto fixes ... Add missing connection field for ProvisionResource. Add diagnostics to the ProvisionResource stream.	8 years ago
Kristin Laemmert	b7dc939080	plugin/discovery: add function to filter list of versions by those which ... support the requested platform. If the newest version of a provider which matches the version constraints does not support the requested platform, filter the list of available versions by platform support and try again.	8 years ago
Kristin Laemmert	5429c8f9d1	plugin/discovery: removing deprecated functions	8 years ago
Kristin Laemmert	41dc1c667f	plugin/discovery provider installer: download providers from the registry ... Terraform will query the public registry at https://registry.terraform.io for providers, instead of https://releases.hashicorp.com.	8 years ago
James Bardin	4add169153	Merge pull request #18601 from hashicorp/jbardin/shims ... helper/schema shims	8 years ago
James Bardin	e8ca467093	legacy provider needs to handle StateUpgraders ... In order to not require state migrations to be supported in both MigrateState and StateUpgraders, the legacy provider codepath needs to handle the StateUpgraders transparently during Refresh.	8 years ago
James Bardin	edfaf22746	add some of the shims used for the grpc provider ... This adds some of the required shim functions to the schema package. While this further bloats the already huge package, adding the helpers here was significantly less disruptive than refactoring types into separate packages to prevent import cycles. The majority of tests here are directly adapted from existing schema tests to provide as many known good values to the shims as possible.	8 years ago
Kristin Laemmert	f2c460cb2f	registry: renaming module-specific registry functions	8 years ago
Kristin Laemmert	57f99389e8	registry: adding provider functions to registry client	8 years ago
James Bardin	2fbc8e12e9	Merge pull request #18586 from hashicorp/jbardin/upgrade-state ... StateUpgrade redux	8 years ago
James Bardin	abf00bea7a	updates to teh StateUpgraders ... Fix documentation. Require StateUpgraders to be add in order, and test in validation.	8 years ago
James Bardin	ddc407d5b0	StateUpgrade redux ... It turns out that state upgrades need to be handled differently since providers are going to be backwards compatible. This means that new state upgrades may still be stored in the flatmap format when used wih terraform 0.11. Because we can't account for the specific version which could produce a legacy state, all future state upgrades need to record the schema types for decoding. Rather than defining a single Upgrade function for states, we now have a list of functions, each of which handle upgrading a specific version to the next. In practice this isn't much different from the way many resources implement upgrades themselves, with a separate function for each version dispatched from the MigrateState function. The only added burden is the recording of the schema type, and we intend to supply tools and helper function to prevent the need to copy the entire existing schema in all cases.	8 years ago
James Bardin	ebc2c59681	Merge pull request #18579 from hashicorp/jbardin/upgrade-state ... add UpgradeState to schema.Resource	8 years ago
James Bardin	cb7514275b	implement UpgradeState for schema.Resource ... This is the provider-side UpgradeState implementation for a particular resource. This new function will be called to upgrade a saved state with an old schema version to the current schema. UpgradeState also requires a record of the last schema and version that could have been stored as a flatmapped state. If the stored state is in the legacy flatmap format, this will allow the provider to properly decode the flatmapped state into the expected structure for the new json encoded state. If the stored state's version is below that of the LegacySchema.Version value, it will first be processed by the legacy MigrateState function.	8 years ago
James Bardin	41cdeda88e	add schema.InternalMap ... This exposes the internal schemaMap for use by the new provider shims.	8 years ago
James Bardin	1afadaf7a4	Merge pull request #18552 from hashicorp/jbardin/flatmap-path ... add PathFromFlatmapKey	8 years ago
James Bardin	75f7e19c68	update the new RequiresReplace function ... Make the function work specifically how we need for RequiresReplace. Skip index changes, any set changes are only recorded as the set itself, and filter out duplicate paths. Add a few more tests to check for various nested structures.	8 years ago
James Bardin	63808f9350	change PathFromFlatmapKey to RequiresReplace ... Rather than try and make a generalized path function here, what we really need in a function to generate the paths needed for RequiresReplace. This needs to take into account that sets elements don't need to be indexed themselves, and changes to collection index values aren't needed.	8 years ago
James Bardin	1b536a2792	add hcl2shim.PathFromFlatmapKey ... PathFromFlatmapKey is used to convert a flatmap key to a cty.Path, and ensures it conforms to the type schema. This is used when handling Diffs, where the ResourceAttrDiffs are indexed by the flatmapped key values, and we need to convert those to addresses to apply to a cty.Value.	8 years ago