When you create a database service + logical database, the UI currently lacks feedback that the RDS database servers are provisioning. The environment doesn't show any database info whatsoever.
--
15 minutes or so later, the Database is provisioned, detected and shown in the UI - appearing out of the blue:
We can detect that there is a database service being created via the API, but we have no identifier as to what environment that database service is going to be a part of. We can use that knowledge to show something to the user...
E.g. Any database services you created for this environment will appear here once server provisioning is complete. Please allow up to 15 minutes for this process.
This text is very general, but better than displaying nothing at all. However it's problematic in certain scenarios:
If you create two environments; say a production and a staging environment, but create a database service for use in just the production one, the UI for both would show the 'provisioning' generic message.
It's the equivilant of us saying "you just created some stuff, it isn't ready yet and we're not sure where it's going to go".
If we can have the API return the database service creation info with an associated Environment ID, any vagueness can be ruled out, and we can then be smarter about showing the provisioning messaging only where it's relevant.
That probably means a bit more API work to accomplish, but less potential for confusing the user and expose guesswork about what an environment may or may not be doing.