16 Commits (76d11f44cc293f4e03dc4e5cc65443c91aef1f23)

Author	SHA1	Message	Date
Martin Atkins	44bc7519a6	terraform: More wiring in of new provider types ... This doesn't actually work yet, but it builds and then panics in a pretty satisfying way.	8 years ago
Martin Atkins	594a821ab3	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	c39e9e107f	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
Martin Atkins	a3403f2766	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
James Bardin	f9fee83279	minor providers.Interface fixes ... Add a missing TerraformVersion field, and fix a TypeName field.	8 years ago
James Bardin	4fedf6c6f4	removing connection data from the providers ... Very few resources need connection info, and rather than relying on providers to set default for some resources, we are going to require that connection blocks be explicitly set in the configuration.	8 years ago
James Bardin	cd53b333f2	add config value to ApplyResourceChange ... Providers will also need the config for reference during apply, in case some of the config values were still unknown during plan.	8 years ago
James Bardin	f77dd12e5c	add Config to the PlanResourceChangeRequest ... In order for providers to determine if a computed value was unset in the configuration, the configuration must be passed along with the prior and proposed states. Terraform core will still handle the creation of the ProposedNewState to ensure correctness, but the raw configuration value will also be supplied for comparison.	8 years ago
Martin Atkins	479c6b2466	move "configschema" from "config" to "configs" ... The "config" package is no longer used and will be removed as part of the 0.12 release cleanup. Since configschema is part of the "new world" of configuration modelling, it makes more sense for it to live as a subdirectory of the newer "configs" package.	8 years ago
Martin Atkins	f77e7a61b0	various: helpers for collecting necessary provider types ... Since schemas are required to interpret provider, resource, and provisioner attributes in configs, states, and plans, these helpers intend to make it easier to gather up the the necessary provider types in order to preload all of the needed schemas before beginning further processing. Config.ProviderTypes returns directly the list of provider types, since at this level further detail is not useful: we've not yet run the provider allocation algorithm, and so the only thing we can reliably extract here is provider types themselves. State.ProviderAddrs and Plan.ProviderAddrs each return a list of absolute provider addresses, which can then be turned into a list of provider types using the new helper providers.AddressedTypesAbs. Since we're already using configs.Config throughout core, this also updates the terraform.LoadSchemas helper to use Config.ProviderTypes to find the necessary providers, rather than implementing its own discovery logic. states.State is not yet plumbed in, so we cannot yet use State.ProviderAddrs to deal with the state but there's a TODO comment to remind us to update that in a later commit when we swap out terraform.State for states.State. A later commit will probably refactor this further so that we can easily obtain schema for the providers needed to interpret a plan too, but that is deferred here because further work is required to make core work with the new plan types first. At that point, terraform.LoadSchemas may become providers.LoadSchemas with a different interface that just accepts lists of provider and provisioner names that have been gathered by the caller using these new helpers.	8 years ago
James Bardin	12521366e1	Add ImportedResource type ... The ImportResourceStateResponse command can return mutliple types. ImportedResource maps the state to the appropriate type name, and also allows providers to return Private data for each resource.	8 years ago
James Bardin	dc78269a3c	use cty.Value for connection info ... For now this will be an encoded map, but it allows for a more complex schema in the future.	8 years ago
James Bardin	960553e18b	rename UpgradedState	8 years ago
James Bardin	6a1b57a1e4	split PriorStateRaw into JSON and Flatmap ... This way the provider doesn't need to be concerned with determining the state encoding.	8 years ago
James Bardin	91b5bbbde0	add versions to the provider schemas ... We need to know the schema version for all resources. This is stored in order to allow providers to upgrade the state from a known previous version.	8 years ago
James Bardin	1473d09c50	rename provider and provisioner packages ... Using plural names to avoid collisions in existing code.	8 years ago