Configurable struct tags about go-cty HOT 2 CLOSED

Hmm... this feels a little tricky to me because the format of the struct tags is not identical between the two... the hcl struct tags have some extra modifiers to choose between block/attribute/etc while the cty ones don't.

It honestly feels weird to me to expose either of these directly to a plugin developer; that seems like some very tight coupling between the plugin API and Nomad's current choice of configuration syntax.

For context, over in Terraform we're using cty/msgpack within the plugin SDK primarily for convenience (since it's a msgpack interface we already know well) but the plugin developer using our SDK never knows about it and, if a developer were not using our SDK (i.e. in future writing a plugin in a different language entirely) it'd be fine for them to just use any old msgpack parser/formatter as long as it fully supports the latest spec.

(We also added an extra higher-level schema layer over the low-level ones in HCL/cty, and while we did that primarily because Terraform needs some additional metadata that the lower-level systems can't represent, it also serves to insulate plugins from these configuration language details in the other direction.)

from go-cty.

Sounds good! We're going to switch to using codec and not referencing cty directly at all. Closing.

from go-cty.