opentofu/internal/command/jsonchecks
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
..
checks_test.go command/jsonplan: Include new-style check results in JSON plan output 2022-08-26 15:47:29 -07:00
checks.go command/jsonplan: Include new-style check results in JSON plan output 2022-08-26 15:47:29 -07:00
doc.go command/jsonplan: Include new-style check results in JSON plan output 2022-08-26 15:47:29 -07:00
objects.go addrs: Be explicit about checkable object address kinds 2022-08-26 15:47:29 -07:00
status.go command/jsonplan: Include new-style check results in JSON plan output 2022-08-26 15:47:29 -07:00