Eric Holmes

Just realized that an `${env ...}` lookup wouldn't actually work for this, since those are only available inside variables, and the env file interpolation is pretty commonly used outside variables.

I was thinking a bit about this recently. Essentially, what this boils down to is storing some kind of state somewhere. In addition to making deletions like this easier, it...

Hi @tobiasmcnulty. The demo environment is simply meant to serve as a quick way to try out an Empire environment. We try to make it explicitly clear that it's not...

@tobiasmcnulty good point. It would be pretty easy to add an option for optionally selecting an ACM/Server cert. I'll re-open this.

So, I think this is a legit race between deploying and setting config. When we deploy, we open a transaction and then lock the releases table to ensure that deployments...

Yeah, this will happen if you restart Empire while it's deploying something, since the stack operation lock will be released when the postgres connection drops.

Yeah, I've hit this before as well. The `domain-*` stuff was always meant to be pulled out before a 1.0 release, since it's mostly cruft leftover from the first version....

Not that it's an issue, just needs to be considered. I think ^ is the right way to approach it.

This one got closed an accident from https://github.com/remind101/empire/pull/803, but very easy to change now. Right now, the cloudformation stack doesn't specify any health checks, which means you can alter the...

To clarify the issue above, this can happen when Empire is configured to forward logs from attached containers to CloudWatch. There's a lot of ways that CloudWatch logs forwarding can...