Brian Morton

Pattern for accepting more activity types

1

Hey! I'm looking at supporting the [other activity types](https://github.com/infracloudio/msbotbuilder-go/blob/develop/schema/model_activity_types.go#L37-L51) that could arise, but it looks like changes to the core library are required to make that possible. Would you be...

Enforcing BlockKit limits

10

In looking to replace our internal BlockKit implementation with this one, something that came up is that we'd lose the support we built for enforcing Slack's BlockKit limits on text...

Plugin support

6

Deployster itself is pretty simple and scoped, but being able to take action after Deployster has done certain things would be pretty awesome. Some examples of things that Deployster likely...

Allow vulcand to be substituted with other alternatives

10

Currently, we assume that vulcand is installed and use that to accomplish zero downtime deploys. We should allow different solutions here, including things like Nginx or HAProxy. Both alternatives would...

CoreOS added a software network fabric for containers called `flannel` in version 554. Basically, it gives every Docker container an IP that is accessible from anywhere in the cluster. For...

Block deployment if currently deploying

9

If a deploy is already in flight for a given service, we should prevent subsequent deploys if that service. We could optionally allow a `force` parameter to cancel and cleanup...

Validate version of deploy before we start

11

Currently, you can pass any version, valid or not, to the `POST` deploys endpoint and we'll attempt to deploy that. Should we do validation first so we can fail earlier?...

Dynamically set env vars passed to `docker run` in unit file based on service's etcd directory

9

Is it reasonable for deployster to implement functionality to ease in setting/managing environment variables that are exposed to services by convention? **Update 3/12**: In deploying a number of services with...

Add synchronous mode for starting a deploy and monitoring the status of the deploy

1

The asynchronous mode of deploys is good for many use-cases and makes things quite a bit simpler, but it leaves the person deploying a little unsure about what is going...

At the present time, we only support the one [hard-coded](https://github.com/bmorton/deployster/blob/6d7d7eb7501418e529792280d6a664b3bda00c31/server/templates.go) unit template. This will probably work for lots of stateless service use-cases, but it definitely won't cover everything. There are...