This message was deleted.

Instead of transforming the password into the full resource transform it into the input that needs it and create the resource outside of apply. This way you'll be able to reference the outputs of the resource

Creating resources within apply is not recommended. It breaks the dependency graph and can cause problems.

It should not break dependency graph anymore, I sent a PR a while ago to fix that. But it is still not recommended

@calm-parrot-72437 as Evan and Luis pointed out, creating the

Instance

resource inside

apply()

is not ideal. You should be able to pass the

password

as an input straight to whichever property uses that value in

new aws.ec2.Instance(…)

. Basically, do this:

const instance = new aws.ec2.Instance("", {
  someProp: password <--
});

for a quick workaround with the code you already have, you can run

pulumi stack output --show-secrets

to reveal secret values in the command-line.

First thing I tried look like this: const instance = new aws.ec2.Instance(appName, { userData: createUserData( ["start_license_server"], { "start_license_server": { commands: { "01_start_server": { command:

start ${password}

, }, }, }, }, ), }); ..but the pulumi update details showed the userData created by pcloudinit package had pulumi warnings in it, so figured i had messed up

when you use an output property in string interpolation you should use “pulumi.interpolate `start ${password}`”

command: pulumi.interpolate

start ${password}

? typescript doesn't like that, it wants a string for command not an Output<string>

Where does the

createUserData

function come from?

As I mentioned in my earlier message, Slack’s code formatting mucked up what I typed. The link I posted above has a few examples of how to use interpolation with resource outputs properties. Since they are special properties, they can’t be used directly in JS string interpolation. They have to be prefixed with

pulumi.interpolate

which is

Output

-aware.

const instance = new aws.ec2.Instance(appName, {
    userData: createUserData(
        ["start_license_server"],
        {
            "start_license_server": {
                commands: {
                    "01_start_server": {
                        command: pulumi.interpolate `start ${password}`,
                    },
                },
            },
        },
    ),
});

I am not sure what your

createUserData

function does, so I can’t guarantee ☝️ will work straightaway.

@clever-sunset-76585 He is right, the input type of

userData

is string instead of

Input<string>

. So typescript will reject it: https://www.pulumi.com/docs/reference/pkg/aws/ec2/instance/#userdata_nodejs

createUserData is from pcloudinit, i.e., https://github.com/joeduffy/pcloudinit

@green-school-95910 in our resource docs we don’t show the types as wrapped types of

Input

or

Output

, but in fact

userData

property of

InstanceArgs

is of type

Input<string>

. Here’s the nodejs docs for that: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/ec2/#InstanceArgs-userData

True, I never noticed that on the resource docs always show the value that comes inside the input. TIL

before userData though we'd be assigning an Output<string> to a string.. where the pulumi.interpolate would be

@calm-parrot-72437 yes, it appears that

command

property only takes a string as you called out, so yeah you are back to transforming the output property with an apply. Can you try this?

const userData = password.apply(p => {
    createUserData(
        ["start_license_server"],
        {
            "start_license_server": {
                commands: {
                    "01_start_server": {
                        command: `start ${p}`,
                    },
                },
            },
        },
    )
});

const instance = new aws.ec2.Instance(appName, {
    userData,
});

i see. thank you, yes will try.

Awesome! Glad it worked.