Hi guys, I have a long-term problem with the mssql provider, (I spare you the details, but I came to the conclusion that I wanted is just not possible) and determined that the automation api is gonna solve exactly my problem. There is something I can't decide how to do cleanly, though. So, I have a kind of meta IAC project managing sub-projects. The question is, is there a standardised way to manage configuration like direct pulumi projects at the higher level? Basically, declare a current stack and configuration at the orchestrating project level, which you can read and launch sub-projects with? I'm thinking about storing secrets in a secret-provider, etc. Of course, I can come up with my custom configuration system at the top project level, but I was wondering if there was any better way to do it. Summary: Pulumi project-style standardized way to handle configuration/secrets for automation projects

Pulumi ESC

Ha, I didn't realise that it was the purpose. Is it smth only pulumi cloud or I can do that on my own setup?