Database Lifecycle Fixes: Names, Stop/Start and Destroy
Several database lifecycle issues are resolved — the database you name is created, stopping no longer wedges, and a destroy is only reported done once it really is.
What's changed
- The database name you supply is now created on PostgreSQL instances
- Stopping an instance no longer wedges, and there is a force-stop recovery path
- The DNS endpoint shown after a stop/start cycle is now correct
- A destroy is reported complete only once the underlying resources are actually gone
- We are alerted when an instance's deployment sync gets stuck, instead of it sitting silently