Hello All, I'm previewing Pulumi and I'm really enjoying it so far....running into an issue with secrets however.... I create a secret using

pulumi config set --secret [name] [value]

, but when I attempt to do

cfg.requireSecret('[name]')

I'm getting an error during

pulumi up

(see screenshot). If I hard code my variable (rather than using config) it works....I've tried the suggestions in the error, I've set the config variable to

plaintext

and used

cfg.require('[name]')

and still doesn't work....I've studied the secrets documentation....am I missing something?

You have to use repositoryToken within the

apply()

closure. Like this:

cfg.requireSecret("repositoryToken").apply(x => useToken(x));

apply

returns an

Output

so you can't use it directly. Although all the Pulumi docs tell you to use

apply

. I actually found it a lot easier to only use Promise with async/await. You can convert an

Output

to a Promise with this:

const fut = new Promise(f => output.apply(f));

yep, Yage is right, if you share your full code we can help, you're likely passing the secret value to a resource parameter that only takes a string

Cool....here is the code:

import * as pulumi from "@pulumi/pulumi";
import * as resources from "@pulumi/azure-native/resources";
import * as applatform from "@pulumi/azure-native/appplatform";
import * as azureweb from "@pulumi/azure-native/web";

const cfg = new pulumi.Config();
const repositoryToken = cfg.requireSecret('repositoryToken');

const frontend = new azureweb.StaticSite("static-site-name", {
    resourceGroupName: "[resourceGroupName]",
    branch: "main",
    name: "static-site-name",
    sku: {
        name: "Free",
        tier: "Free"
    },
    repositoryUrl: "[repositoryUrl]",
    repositoryToken: repositoryToken
});

It's unclear to me from the docs when lifting works and when it doesn't. From my anecdotal experience it's a pain to hope lifting works and find out later that it resulted in garbage value. I just use await to make the code nicer to write and read. It's been working well for me so far. My understanding is

apply

and async/await accomplish the same thing. But with async/await you don't get callback hell.