No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Would a relative directory work? `vault:ca_cert_dir ./pogos2/certs`?

yeah, i could commit the cert to my pulumi repo and probably get away with a relative path

but if you start multiplying that pattern it gets annoying pretty quickly

on my setup I had some layer of python on top of pulumi, it would inject ENV vars for dynamic things like build IDs in at runtime on pulumi, then in the typescript code can do:

```        // SERVICE KEY from outside
        if ( typeof(process.env['TASK_REVISION']) === 'undefined' ) {
            console.log("TASK_REVISION env var missing! Please specify it with `pulumi up`");
        }
        var task_revision = String(process.env['TASK_REVISION']);```

but any type of CI you should be able to add the env vars on the pulumi up command like `TASK=123 GROUP=test pulumi up`