Files
opentf/internal/command
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
..
2022-08-22 10:59:12 -07:00
2021-08-17 15:20:05 -07:00
2022-08-22 10:59:12 -07:00
2022-08-22 10:59:12 -07:00
2021-05-17 14:09:07 -07:00
2022-08-22 10:59:12 -07:00
2021-05-17 14:09:07 -07:00
2021-05-17 14:09:07 -07:00
2022-08-22 10:59:12 -07:00
2021-10-28 11:51:39 -04:00
2021-05-17 14:09:07 -07:00
2022-03-30 09:52:49 +01:00
2022-08-01 16:38:03 -05:00
2021-05-17 14:09:07 -07:00
2021-05-17 14:09:07 -07:00