For resources that don't support tagging or user-defined naming, you'll need state.
> Furthermore, tagging is restrictable by IAM, is often co-opted by finance for cost allocation, and is subject to often-bizarre limits about what the content can be (even more so across providers).
You can fix your IAM. Cost allocation tags are treated specially.
> Finally, how would you manage tags as an actual resource themselves in this model?
> Furthermore, tagging is restrictable by IAM, is often co-opted by finance for cost allocation, and is subject to often-bizarre limits about what the content can be (even more so across providers).
You can fix your IAM. Cost allocation tags are treated specially.
> Finally, how would you manage tags as an actual resource themselves in this model?
Why would you do that?