Bill Farner

Some relevant discussion in #214

@chungers i was not suggesting restoring TCP support, just pointing to context. In particular, this line from the issue description: > TCP support is primarily offered as a lowest-common denominator...

Can you elaborate on the UX? Doing so before breaking ground on code will be extremely helpful for others to collaborate during development, and have a shared vision of where...

The proposal above leaves me unclear on the UX problem being addressed. I was anticipating that this effort would focus on relieving the user of managing startup of plugins for...

> Are there specific examples of 'added complexities' you are referring to? I gave myself the impression that config files were splitting apart each plugin configuration into separate files. The...

@chungers aren't all of your concerns alleviated by the fact that using a go plugin is a choice? The proposal is to _add_ support for plugins, not to remove or...

> Flavor's Drain should be chained to the Instance's Destroy That's exactly what i was thinking. There are some use cases that we should anticipate (but probably not solve yet)...

Instance tracking is the responsibility of the instance plugin. I would not recommend storing instance state in a file, for the reason you note in addition to high availability. In...

You could configure your plugin to accept a globally-accessible store, e.g. S3. On the InfraKit side, we're starting to add persistent state, but it's unclear if/when/how that would be exposed...

I'm thinking of S3 as a benefit to provide high availability and better durability than a local file.