[josep2]

Congratulations on the release! I have a question about the YAML DSL for ESC. Yaml is pretty convenient and easy to read when there isn't a lot of nesting but it can become unwieldy quickly and hard to make sense of, especially when you are referencing other fields. How good is the linting/intellisense to figure out if you are making a mistake in your references without having to compile?

[lukehoban]

Agreed that YAML (and JSON) can be difficult to manage at large scale. This is actually a big part of why Pulumi ESC exists, to be able to decompose large YAML/JSON configuration files into smaller logical and composable units.

As you note, intellisense and error squiggles can also help a lot here - both for ensuring references to other environments are correct, and to get checking for your dynamic secrets providers. We’ve added the Monaco editor (from VS Code) into the Pulumi Cloud console to make it easier to offer these features in the very near future.

We also offer a preview pane to make it easy to play interactively validate your environments documents while working on them directly in the console.

Lots more coming for providing an even richer experience working with environments in Pulumi ESC.

[verdverm]

You can use CUE with the Pulumi `runtime: compiler: ...`

https://www.pulumi.com/blog/extending-pulumi-languages-with-...

https://www.pulumi.com/docs/languages-sdks/yaml/#compiler-su...

[josep2]

This is super helpful. Thank you

[verdverm]

You can find me in the CUE slack if you need more help

cheers!