Move resource creation in ResourceReadyEvent event

[sebastienros]

Description

I am testing the new ResourceReadyEvent. However there is a limitation in this case, I would still prefer the previous solution. Resource creation (db, containers) needs to happen when the emulator is "ready". But dependents should not use cosmosdb until the resources are created.

The previous solution was relying on a custom healthcheck to create and assess the db/containers are created and/or ready. This new solution is hitting a deadlock, that is the ResourceReadyEvent is triggered once the resource si healthy, but if the healthcheck ensure the db/containers are available then it can't work since ResourceReadyEvent is doing it. So right now no db/containers are passed in the healthcheck, so it will only ensure the service is available before ResourceReadyEvent can create the db/containers.

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

[eerhardt]

This looks more like what I expect. But maybe thinking about it more .... not considering the resource to be "healthy" until the database is created might be the right thing to do....

[davidfowl]

We can do that as a follow up to this #7163