community 
concurrent environment command support for setup
i would like to run ExecuteEnvironmentCommand during my setup.
i need to run a blueprint command as part of my setup, and cannot just enqueue it, as the result of the setup might rely on that command.
also, if setup just queues these commands then the setup might end before them, and the sandbox will become active prematurely, which is not good when having automated tests waiting for active state
I didn't say we need a new key, there might be other ways to solve it, like marking a specific setup script as one that is going to need concurrency, etc.
I'm just saying that allowing it for setup/teardown might be more relevant than allowing it for any other orchestration command (which is the key that exists today).
6 People are following this .
