feat: Add "coder_metadata" resource #34
Conversation
| Optional: true, | ||
| Default: false, | ||
| }, | ||
| "is_null": { |
There was a problem hiding this comment.
Would we just assume an empty string is null? Maybe that's too lossy?
There was a problem hiding this comment.
Possibly! I implemented it this way because the original ticket asked for null support, and I figured somebody who's used to Terraform's semantics wouldn't necessarily be expecting us to conflate null and "" the way Go does. But if we're OK with that behavior, I definitely wouldn't mind getting rid of this hack.
Done! I added an example as well.
Hmm, a few other possibilities that come to mind:
|
| pair { | ||
| key = "pod_uid" | ||
| value = kubernetes_pod.dev[0].uid | ||
| } |
There was a problem hiding this comment.
I was confused about why key and value were nested until @kylecarbs explained to me that HCL allows multiple pair blocks. We should demonstrate that here.
There was a problem hiding this comment.
Good point! I updated the example to use multiple blocks, and also to demonstrate the sensitive attribute.
I do like Some other options:
And some more "out there" options:
I'd read these as "attach/add key value to coder metadata". |
|
|
This PR adds support for the
coder_metadataresource, which allows attaching arbitrary key/value metadata to other resources in a template, as described in coder/coder#2989.