Hi, I am starting to use pulumi ESC as env & secret manager. One question I have is this: Are we supposed to keep & modify all the env variables in the pulumi cloud IDE? It might become unwiedly to use after some time. I was thinking if there was a way to at least download the env definition and keep track of it in source control and the local IDE (and by env definition I mean, the type and names of the env variables, not necessarily their values). I am also thinking how to integrate pulumi with other systems. For example, vercel requires to download a

VERCEL_OIDC_TOKEN

exclusively for local development (when doing OIDC integration). So one would run

vercel env pull

to get this value. How are you meant to use it now? Surely not by going online and modifying the pulumi environment there, copying the token you just downloaded? I guess a similar question applies when you want to have a (slightly) different environment for each developer, for e.g. local testing. You don't want everyone to modify the

.dev

environment online, but something needs to happen locally. I am aware these are broad questions, but I am just trying to understand how you envision the usage of Pulumi ESC, and how it all integrates into the day to day work of each developer. Thanks a lot!