Hi all, I'm new to ESC and going through the documentation, I feel that I'm missing something... I'm developing a webapi in .net 9. I want to manage the runtime secrets in pulumi cloud using pulumi esc, and I want to access configuration and secrets using the options pattern. My requirements are: 1. support local development config/secrets 2. support local testing (running in docker using test containers and xUnit) 3. support CI pipeline testing (using github actions) 4. support deployed environments (running google cloud run and using gcp secret manager) I was thinking of creating an pulumi esc environment for each of these use cases (so for example, for local development each developer will have their own pulumi esc environment etc) I can't find anywhere how to load config and secrets from a pulumi esc environment via code in c#. What am I missing?

The ESC SDK isn't available in C# right now, unfortunately.

Thanks @stocky-restaurant-98004. Does this mean that Pulumi ESC isn't an option for me? Is there a work around by setting the secrets as env variables in docker? If there's a way for each of the scenarios above to read secrets from Pulumi cloud and run containers with the secrets as environment variables? If it's possible then could you please point me at some examples of how to do it?

Are you running on Kubernetes?

to add to what Josh said: while we don't currently have .NET support, it is on our radar and we have an issue for it. In the meantime you can use the esc CLI or use the ESC API directly

Hi, thanks both 🙂 I think I'll go down the REST Api route as it feels like the easiest to swap to the .NET provider when it's available

I created a wrapper based on how the .net envkey sdk worked along with a configuration provider. https://www.nuget.org/packages?q=esc+bytefoo&includeComputedFrameworks=true&prerel=true&sortby=relevance https://github.com/bytefoo/esc-sdk-cli https://github.com/bytefoo/extensions-configuration-esc

@bored-activity-40468 I'm spending a bit more time on this. Is there a reason why you're using executables rather than calling the REST API?

Hi, thanks for pointing this out. Yup, the docs are outdated here, we will get this fixed. The output of the open API call is the full detailed expression tree. If you want to see how this is converted to a "human friendly" output, https://github.com/pulumi/esc/blob/main/cmd/esc/cli/env_open.go is where it's done in esc, but it might be easier to use the esc CLI in your case

Thanks @freezing-pilot-97749. I'd rather move away from the CLI approach. For example, with the CLI approach, when running the code locally in an IDE (rider) it works fine but when using

docker compose up

we're getting a permission denied to run the CLI from its target folder in the container... using the API will avoid things like this + it works on all platforms, unlike the CLI that requires 3 executables to be shipped with the code

@big-king-63459 Used the executable because it was a quick replace since envkey was shutting down. I believe the executable has some functionality built on top of the rest API but I could be wrong. Our stuff runs in containers and when the container is built esc gets permissions to run so it can execute. I used openapi-generator and kiota to generate a client which works fine but work needs done on the templates and extensions the other sdks have.

Thanks @bored-activity-40468 🙂 Even though the code runs in containers it still caused me some issues around permissions etc (see above). I changed the code to use the REST API and it's working well for me. I built it specifically for my app, and also only implemented the functionality that I needed (Init, Open and Get).

I had hopes that the c# pulimi esc sdk would have been available by now.

Good point @bored-activity-40468. @freezing-pilot-97749, @stocky-restaurant-98004 any news on that front?

@big-king-63459 Here's what I have to do to for esc to work in the image. Yeah, the rest api / sdk would be ideal.

@big-king-63459 unfortunately not yet