search

micro / services

Real World Micro Services
Apache License 2.0
1.27k stars 139 forks source link

App(Beta) - List and Run are showing conflicting results after Deployment had failed. #336

Open lambdaR opened 2 years ago

lambdaR commented 2 years ago

When you rerun app.Run again after deployment had failed with the same Name each endpoint returns different result, Run return this {"Id":"app.run","Code":400,"Detail":"pwm3oappszeus3 already running","Status":"Bad Request"} and List returns this {zeus 2021-12-16T14:33:14.046968432Z map[] pwm3oappszeus3 pwm3oappszeus3 8080 us-central1 github.com/lambdaR/playing-with-m3o-apps DeploymentError https://pwm3oappszeus3.m3o.app} also status returns this {"Id":"app.status","Code":400,"Detail":"service does not exist","Status":"Bad Request"}

asim commented 2 years ago

What should be the expected behaviour? You'll need to delete and recreate.

lambdaR commented 2 years ago

Well, if the cause of future errors (Deployment) is not M3O but the provider, then it would be much helpful for the developer who is using app.Run if the returned message was something like ‘Deployment Error, delete and try again’ not Running.