terraform

Commit Graph

Author	SHA1	Message	Date
Paul Tyng	bb9ae50279	Copy TF version to helper/schema provider	7 years ago
James Bardin	46b4c27dbe	create a SimpleDiff for the new provider shims Terraform now handles any actual "diffing" of resource, and the existing Diff functions are only used to shim the schema.Provider to the new methods. Since terraform is handling what used to be the Diff, the provider now should not modify the diff based on RequiresNew due to it interfering with the ignore_changes handling.	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
Stefan Schmidt	ee6c8a777a	s/repalce/replace	8 years ago
Chris Marchesi	8af9610b87	helper/schema: Hook CustomizeDiffFunc into diff logic It's alive! CustomizeDiff logic now has been inserted into the diff process. The test_resource_with_custom_diff resource provides some basic testing and a reference implementation. There should now be plenty of test coverage for this feature via the tests added for ResourceDiff, and the basic test added to the schemaMap.Diff test, and the test resource, but more can be added to test any specific case that comes up otherwise.	9 years ago
Martin Atkins	183833affc	core: terraform.ResourceProvider.GetSchema method In order to parse provider, resource and data source configuration from HCL2 config files, we need to know the relevant configuration schema. This new method allows Terraform Core to request these from a provider. This is a breaking change to this interface, so all of its implementers in this package are updated too. This includes concrete implementations of the new method in helper/schema that use the schema conversion code added in an earlier commit to produce a configschema.Block automatically. Plugins compiled against prior versions of helper/schema will not have support for this method, and so calls to them will fail. Callers of this new method will therefore need to sniff for support using the SchemaAvailable field added to both ResourceType and DataSource. This careful handling will need to persist until next time we increment the plugin protocol version, at which point we can make the breaking change of requiring this information to be available.	9 years ago
Radek Simko	07cbd54fbc	Actively disallow reserved field names in schema (#15522 )	9 years ago
James Bardin	1d9d7be28c	Add schema.Provider.TestReset method Provider.TestReset resets the internal state of the Provider at the start of a test. This also adds a MetaReset function field to schema.Provider, which is called by TestReset and can be used to reset any other tsated stored in the provider metadata. This is currently used to reset the internal Context returned by StopContext between tests, and should be implemented by a provider if it stores a Context from a previous test.	9 years ago
Mitchell Hashimoto	5ee8042dff	helper/schema: expose stop information as a Context	10 years ago
Mitchell Hashimoto	d1bb2f3487	helper/schema: support Stop()	10 years ago
Mitchell Hashimoto	60140b28f4	Revert "Merge pull request #9536 from hashicorp/f-provider-stop" This reverts commit `c3a4cff133`, reversing changes made to `791a02e6e4`. This change requires plugin recompilation and we should hold off until a minor release for that.	10 years ago
Mitchell Hashimoto	86eb30b8a2	helper/schema: expose stop information as a Context	10 years ago
Mitchell Hashimoto	8c11f137f5	helper/schema: support Stop()	10 years ago
Radek Simko	b90ab0b705	schema: Return all validation errors together from InternalValidate	10 years ago
Martin Atkins	6a468dcd83	helper/schema: Resource can be writable or not In the "schema" layer a Resource is just any "thing" that has a schema and supports some or all of the CRUD operations. Data sources introduce a new use of Resource to represent read-only resources, which require some different InternalValidate logic.	10 years ago
Martin Atkins	0e0e3d73af	core: New ResourceProvider methods for data resources This is a breaking change to the ResourceProvider interface that adds the new operations relating to data sources. DataSources, ValidateDataSource, ReadDataDiff and ReadDataApply are the data source equivalents of Resources, Validate, Diff and Apply (respectively) for managed resources. The diff/apply model seems at first glance a rather strange workflow for read-only resources, but implementing data resources in this way allows them to fit cleanly into the standard plan/apply lifecycle in cases where the configuration contains computed arguments and thus the read must be deferred until apply time. Along with breaking the interface, we also fix up the plugin client/server and helper/schema implementations of it, which are all of the callers used when provider plugins use helper/schema. This would be a breaking change for any provider plugin that directly implements the provider interface, but no known plugins do this and it is not recommended. At the helper/schema layer the implementer sees ReadDataApply as a "Read", as opposed to "Create" or "Update" as in the managed resource Apply implementation. The planning mechanics are handled entirely within helper/schema, so that complexity is hidden from the provider implementation itself.	10 years ago
Mitchell Hashimoto	c02c6c3f9c	helper/schema: default state func for import	10 years ago
Mitchell Hashimoto	2bb814e3de	helper/schema: adapt to ID being arg to ImportState	10 years ago
Mitchell Hashimoto	03931bfda9	helper/schema: ImportState must set ID on the resource data	10 years ago
Mitchell Hashimoto	445194ebdf	helper/schema: test ImportState	10 years ago
Mitchell Hashimoto	1685054a9a	helper/schema: cleaner way to store Ephemeral	10 years ago
Mitchell Hashimoto	84531a3fd5	helper/schema: sets Importable to true for resources that have importer	10 years ago
Mitchell Hashimoto	e36597cad7	helper/schema: internal validate as part of provider validation [GH-1291]	11 years ago
Paul Hinze	1e3d1b07e6	helper/schema: validate ConflictsWith against top-level The runtime impl of ConfictsWith uses Resource.Get(), which makes it work with any other attribute of the resource - the InternalValidate was only checking against the local schemaMap though, preventing subResource from using ConflictsWith properly. It's a lot of wiring and it's a bit ugly, but it's not runtime code, so I'm a bit less concerned about that aspect. This should take care of the problem mentioned in #1909	11 years ago
Mitchell Hashimoto	5aed997223	helper/schema: Input support	12 years ago
Mitchell Hashimoto	9b2b3a963f	ResourceDiff => InstanceDiff	12 years ago
Mitchell Hashimoto	81d9d70296	helper/schema: conforms to new API, tests pass	12 years ago
Mitchell Hashimoto	3a6940d715	helper/schema: test cases around unknown variable values	12 years ago
Mitchell Hashimoto	0c9b65f3f4	helper/schema: documentation	12 years ago
Mitchell Hashimoto	968a567499	helper/schema: ability to force set Meta	12 years ago
Mitchell Hashimoto	513596cc37	providers/heroku: Heroku app is mostly converted	12 years ago
Mitchell Hashimoto	d321240042	helper/schema: Provider implements ResourceProvider	12 years ago
Mitchell Hashimoto	894187ec18	helper/schema: Resource.Refresh	12 years ago
Mitchell Hashimoto	7db585c257	helper/schema: fix test	12 years ago
Mitchell Hashimoto	afd3a7b811	helper/schema: Provider.Resources	12 years ago
Mitchell Hashimoto	eaac13dd9b	helper/schema: ResourceProvider.Configure	12 years ago
Mitchell Hashimoto	e5e4437351	helper/schema: start Provider	12 years ago

37 Commits (e024960c745f0a464cb081d04765d93f94deaba0)