Martin Atkins 0e4e9f7706 addrs: Be explicit about checkable object address kinds ... Previously we were attempting to infer the checkable object address kind of a given address by whether it included "output" in the position where a resource type name would otherwise go. That was already potentially risky because we've historically not prevented a resource type named "output", and it's also a forward-compatibility hazard in case we introduce additional object kinds with entirely-new addressing schemes in future. Given that, we'll instead always be explicit about what kind of address we're storing in a wire or file format, so that we can make sure to always use the intended parser when reading an address back into memory, or return an error if we encounter a kind we're not familiar with.		2022-08-26 15:47:29 -07:00
..
condition.go	command/jsonplan: Include new-style check results in JSON plan output	2022-08-26 15:47:29 -07:00
doc.go	Move command/ to internal/command/	2021-05-17 14:09:07 -07:00
module.go	Move command/ to internal/command/	2021-05-17 14:09:07 -07:00
plan.go	command/jsonplan: Include new-style check results in JSON plan output	2022-08-26 15:47:29 -07:00
plan_test.go	json-output: Fix unknowns for tuples and sets	2022-06-13 14:33:40 -04:00
resource.go	json-output: Previous address for resource changes	2021-09-20 15:25:23 -04:00
values.go	json-output: Add output type to JSON format	2022-04-27 13:30:15 -04:00
values_test.go	json-output: Add output type to JSON format	2022-04-27 13:30:15 -04:00