store resource state as part of environment #6522
Description
It would be nice for azd to store some information about resources created in an environment.
This would help with querying/interacting with Azure resources from azd in a more robust and performant fashion. A few use cases that this would contribute towards:
- Looking up resources for a given service
- Determine if resources have been provisioned (
azd deploy,azd env remove) - Showing information in
azd show(we've started on ashowspecific implementation with Add file-based caching toazd showfor ~60x performance improvement #6418) - ... for extensions to obtain the same information timely
I am intentionally leaving this issue brief for now. Aspects of what should be stored are worthy of discussion. There are constraints about current Bicep/ARM tooling that may limit us in some areas as we work towards prototyping/implementing.