Will Gibson

Admittedly, I'm currently doing something a bit unusual with Behat to try and fairly efficiently replicate an intermittent bug, but I could do with this feature too. That said, I...

This is address in https://github.com/fagiani/apt-buildpack/pull/26.

We could do with `copilot pipeline package` too. We are using overrides to get things the way we need them and, sadly, the first time we get to see the...

Hi @Lou1415926, Yes, we are still seeing the issue. I guess it's some kind of networking problem. It's sad that there are no logs for the health check requests/responses, so...

There doesn't seem to be anything helpful corresponding to when the problem has occurred in the Task's Events tab, just some `port 443 is unhealthy in target-group` which does not...

`Resources.TargetGroup.Properties.HealthCheckPort` is `8080`, which is what the `nginx` container is set to serve stuff up on. Increasing the grace period is OK. If the problem doesn't distract us any more...

> I think it'd be helpful if the TargetGroup page can show more information (e.g. the actual response code received, or whether it has timed out). While you're passing on...

Using ! in the type to indicate a breaking change is part of the Conventional Commit standard... https://www.conventionalcommits.org/en/v1.0.0/?ref=blog.formacao.dev#commit-message-with--to-draw-attention-to-breaking-change Why would we want to prevent it?

As I understand it, indicating a breaking change is meant to be a single `!` after the type, e.g. `feat!: some commit message`. I ended up here by mistake though,...