Eric Holmes

Support placement constraints/strategy in Procfile

1

We don't have an issue tracking this yet. Placement constraints are a great way to specify the machine/security requirements for an application http://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-constraints.html This should be supported in the Procfile...

This was brought up internally. It could be nice to pull in the `EMPIRE_*` env vars into `emp env`. Some are process specific (e.g. `EMPIRE_PROCESS`, `EMPIRE_PROCESS_SCALE`) so we can't include...

Or only procs with `noservice: true`. At the moment, this error out, since it tries to create a CloudFormation stack with no resources.

Possible race between setting config and deploying

1

We saw an instance today where a config var was set, then a deployment went out around the same time. `emp releases` shows something like this: ``` v1234 Set FOO...

If we could provide an implementation of [this](https://github.com/remind101/empire/blob/ac27a91f3a5131b18700c350ca510d1befed7a51/extractor.go#L25) interface, it could simplify how we currently run Empire, removing the dependency on a Docker daemon completely.

Custom::EmpireAppEnvironment resource behaves strangely if you change resource name

1

Say you have a `Custom::EmpireAppEnvironment` resource in your template with the resource name `AppEnvironment`. If you then change the resource name to something else, like `EmpireAppEnvironment`, you end up with...

Couple of things that I noticed while doing the latest release that could be improved: * [ ] Include a template in the release notes * [ ] Always build...

Outputs don't appear in DescribeStack apparently, so you see this when you do `emp ps`: ```console $ emp ps error: stack didn't provide a "Services" output key ```

If an app has a large number of entries in the Procfile, it's possible to hit the limit on the number of resources in the template (200). Right now (when...