Miserable experience changing ports on App Runner

App Runner looks like is in a deadlock if you need to change your container port.

Suppose you have PORT 8080 set up, and you want to change to 9090.

If you change the port in the current image, the service will fail and revert. But not before wasting 20 minutes of your time before unlocking.

On the other hand, if you try to update the image, then it will also fail and revert back to the old image. Also taking 30 minutes of your life before unlocking.

This runtime <> configuration dependency is too strong, and coupled with the service extremely long deploy durations until failure is really a no-go for high-availability. You're in trouble if you make a simple mistake, specially if the infrastructure process is not flexible in your company.

Looks like the only solution is to try and use the CLI and update everything at once. I'll try that.

If that doesn't work I'll be forced to delete and re-create the service it seems.