mysterious-oyster-8665903/12/2021, 1:06 AM
). So, ideally #1 would occur first with its own
and then - after that entire deployment is complete - automatically do the same for #2 but somehow be able to be aware of and use resources that were changed/deleted/added from #1. Finally, being able to “tear” all this down in an automated way would be fantastic, but that’s secondary for now. What your advice for approaching this use-case?