28 Commits (e2b6ccad8a755fb9ea1b32fb71eec02216438111)

Author	SHA1	Message	Date
James Nugent	074545e536	core: Use .% instead of .# for maps in state ... The flatmapped representation of state prior to this commit encoded maps and lists (and therefore by extension, sets) with a key corresponding to the number of elements, or the unknown variable indicator under a .# key and then individual items. For example, the list ["a", "b", "c"] would have been encoded as: listname.# = 3 listname.0 = "a" listname.1 = "b" listname.2 = "c" And the map {"key1": "value1", "key2", "value2"} would have been encoded as: mapname.# = 2 mapname.key1 = "value1" mapname.key2 = "value2" Sets use the hash code as the key - for example a set with a (fictional) hashcode calculation may look like: setname.# = 2 setname.12312512 = "value1" setname.56345233 = "value2" Prior to the work done to extend the type system, this was sufficient since the internal representation of these was effectively the same. However, following the separation of maps and lists into distinct first-class types, this encoding presents a problem: given a state file, it is impossible to tell the encoding of an empty list and an empty map apart. This presents problems for the type checker during interpolation, as many interpolation functions will operate on only one of these two structures. This commit therefore changes the representation in state of maps to use a "%" as the key for the number of elements. Consequently the map above will now be encoded as: mapname.% = 2 mapname.key1 = "value1" mapname.key2 = "value2" This has the effect of an empty list (or set) now being encoded as: listname.# = 0 And an empty map now being encoded as: mapname.% = 0 Therefore we can eliminate some nasty guessing logic from the resource variable supplier for interpolation, at the cost of having to migrate state up front (to follow in a subsequent commit). In order to reduce the number of potential situations in which resources would be "forced new", we continue to accept "#" as the count key when reading maps via helper/schema. There is no situation under which we can allow "#" as an actual map key in any case, as it would not be distinguishable from a list or set in state.	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
Mitchell Hashimoto	b728e55861	helper/schema: Resource.Data should set latest schema version	10 years ago
Mitchell Hashimoto	b8121ea63e	helper/schema: Resource.Data to return a ResourceData for a Resource	10 years ago
Radek Simko	4c6ceef9b8	helper/schema: Allow identification of a new resource in update func	10 years ago
Panagiotis Moustafellos	e4845f75cc	removed extra parentheses	11 years ago
Radek Simko	641b701830	schema: Make validation more strict	11 years ago
Paul Hinze	7eb72e7a12	helper/schema: record schema version when destroy fails ... This was just a missed exit from the resource.Apply function - subsequent refreshes would add the SchemaVersion back into the state, but having the state recorded once without the meta information can cause problems with Atlas's remote state checksumming.	11 years ago
Mitchell Hashimoto	dd24ed4b76	helper/schema: blank ID refresh doesn't exist [GH-1905]	11 years ago
Justin Campbell	bb14bfa657	helper/schema: call InternalValidate w/ schemaMap{}	11 years ago
Paul Hinze	3ba8ed536b	helper/schema: record schema version on apply ... We were previously only recording the schema version on refresh. This caused the state to be incorrectly written after a `terraform apply` causing subsequent commands to run the state through an unnecessary migration.	11 years ago
Paul Hinze	3d4b55e557	helper/schema: schema versioning & migration ... Providers get a per-resource SchemaVersion integer that they can bump when a resource's schema changes format. Each InstanceState with an older recorded SchemaVersion than the cureent one is yielded to a `MigrateSchema` function to be transformed such that it can be addressed by the current version of the resource's Schema.	11 years ago
Mitchell Hashimoto	466a54cfe4	Merge pull request #766 from hashicorp/f-exists-api ... helper/schema: Exists API	11 years ago
Mitchell Hashimoto	448887f3c4	helper/schema: map counts in state	11 years ago
Mitchell Hashimoto	48b9614556	helper/schema: Exists API	11 years ago
Mitchell Hashimoto	d0ce67a5b7	helper/schema: on destroy/create, reset state to be empty [GH-464]	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	5fc41cc272	helper/schema: properly put "id" into attributes	12 years ago
Mitchell Hashimoto	021a23fe99	helper/schema: if update sets the ID to blank, it deletes the resource	12 years ago
Mitchell Hashimoto	2444986fe8	helper/schema: nice error if update isn't supported	12 years ago
Mitchell Hashimoto	c418681cc3	helper/schema: create/update/delete should work for Resource	12 years ago
Mitchell Hashimoto	894187ec18	helper/schema: Resource.Refresh	12 years ago
Mitchell Hashimoto	51a44db6c2	helper/schema: move InternalValidate to schemaMap	12 years ago
Mitchell Hashimoto	a33e4bcdf0	helper/schema: properly validate sub-resources	12 years ago
Mitchell Hashimoto	7bc0be4b81	helper/schema: couple more tests around Computed (+ fix)	12 years ago
Mitchell Hashimoto	7f14708e71	helper/schema: list ForceNew	12 years ago
Mitchell Hashimoto	01b6b5f48e	helper/schema: initial work	12 years ago