Alternative to account node dependency #1020
Description
We're exploring adopting cdk-organizations for our existing org and are wondering if there isn't a cleaner solution to declaring multiple accounts.
We have a lot of existing accounts that we'll be importing and we also plan to use cdk to create new accounts.
Do you have any recommendations? We're considering making each account its own stack in order to force deploying separately (don't love it). Maybe someone has come up with their own solution?