You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tested what you had on the "Troubleshooting" section of the README and I thought that I was going to see the logs showed on ECS deployment events.
Maybe is not the intention, but the action is not being very useful on my use case. In my use case, the developers are constantly creating deployments and when it fails they are not all capable to see and determine the root cause of failure. I want to be able to output the latest events logs and give some guidance so the devs can troubleshoot on their own.
Also I want to create failure on the workflow run if the deployment didn't go well. that way they are also aware that revision needs to be made.
The text was updated successfully, but these errors were encountered:
I was about to search or create a solution for this.
In our case things are worse, as for production deploymentis we have the circuit breaker enabled, along with rollback to previous state. Then it can happen that the github action ends with sucess code, while the deployment is rolled back (and successful).
I think this will need a new PR apart from #454, but it can provide a good starting point.
I tested what you had on the "Troubleshooting" section of the README and I thought that I was going to see the logs showed on ECS deployment events.
Maybe is not the intention, but the action is not being very useful on my use case. In my use case, the developers are constantly creating deployments and when it fails they are not all capable to see and determine the root cause of failure. I want to be able to output the latest events logs and give some guidance so the devs can troubleshoot on their own.
Also I want to create failure on the workflow run if the deployment didn't go well. that way they are also aware that revision needs to be made.
The text was updated successfully, but these errors were encountered: