Martin Taillefer

Supporting structs as a first class attribute type has considerable implications. Whereas Mixer generally ensures strong typing, this would introduce weak typing into our model. It would also likely require...

This epic, like many epics, continues to be useful beyond the scope of a single release.

Hmmm. What we have now is that the operator specifies: color: "blue" I'd like it to be: in template: enum { RED, GREEN, BLUE} in config: color: BLUE and you're...

So we get the right thing in the template and in the adapter, but the config format is a bit awkward. It sounds reasonable. Do you think if/when we actually...

For #2, adding the Type.Name field is for good style. It's just not great to have a named object and the only place where it's name is kept is in...

The second form would need to be: HandleFoo(context.Context, map[string][]*foo.Instance) since there can be multiple instances for a given type.

I disagree that there is an issue here. The data being provided is in the most directly meaningful form for the adapter author. I do think we should add a...

Can this be closed?

I think this is a reasonable addition, it can't hurt. On a related topic, given an adapter, how do we expect an operator to know the kind of instance to...

Nope, this is different. #1045 is about generating a single functioning noop adapter that can handle all templates we know about. This is about generating a to-be-filled-in adapter skeleton that...