Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
when a service deployment fails due to misconfiguration allow the configuration to be modified in service states besides "running" or "paused" (such as CREATE_FAILED)
in my case an error in an environment variable caused the app to crash during startup. there is no way to remedy this as trying to save changes to configuration environment variables is locked with error (this is from console but same from CLI):
Update service failed - invalid state
Service status must be RUNNING or PAUSED to be updated
this is a catch-22 as the service page Actions only allows delete to be selected (pause and resume are grayed out).
Describe alternatives you've considered
the only alternative appears to be to delete the entire service and start from scratch
Additional context
it would be nice to cancel the deployment when application logs show errors. if the app exits due to error that should be detected before waiting for health checks. instead it ran an additional 15 mins of trying to health check before finally failing.
this may be expected behavior normally (as it tries to revert to previous deployment) but on a first deployment (where config issues are most prevalent) there is nothing to fall back to so it is just burning time
Community Note
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
when a service deployment fails due to misconfiguration allow the configuration to be modified in service states besides "running" or "paused" (such as
CREATE_FAILED)in my case an error in an environment variable caused the app to crash during startup. there is no way to remedy this as trying to save changes to configuration environment variables is locked with error (this is from console but same from CLI):
this is a catch-22 as the service page Actions only allows delete to be selected (pause and resume are grayed out).
Describe alternatives you've considered
the only alternative appears to be to delete the entire service and start from scratch
Additional context
it would be nice to cancel the deployment when application logs show errors. if the app exits due to error that should be detected before waiting for health checks. instead it ran an additional 15 mins of trying to health check before finally failing.
this may be expected behavior normally (as it tries to revert to previous deployment) but on a first deployment (where config issues are most prevalent) there is nothing to fall back to so it is just burning time