This message was deleted.

sparse-intern-71089

09/28/2021, 6:41 PM

This message was deleted.

red-match-15116

09/28/2021, 6:48 PM

Hey! The

preview

is unfortunately incorrect. At the time of preview, pulumi doesn’t know the actual type, however we incorrectly print that as

Output<string>

when it should just be

Output

. There’s an issue one sec.

red-match-15116

09/28/2021, 6:49 PM

https://github.com/pulumi/pulumi/issues/7716

polite-mechanic-60124

09/28/2021, 6:55 PM

Well I at least feel better knowing that my hypothesis was correct. Thank you

polite-mechanic-60124

09/28/2021, 6:57 PM

Are there any suggested workarounds?

red-match-15116

09/28/2021, 7:25 PM

Hmm… can you help me understand what the concern is? The output to

Output.all

is always either

Output[List]

Output[Mapping]

- it’s just that the CLI output is misleading…

red-match-15116

09/28/2021, 7:26 PM

Would it be better if as the issue suggests it is printed as

output<?>

output<T>

? Instead of

output<string>

polite-mechanic-60124

09/28/2021, 7:34 PM

So the issue is that I'm passing job_vars to a resource that requires a mapping (specifically I'm passing it to the vars field in https://www.pulumi.com/docs/reference/pkg/nomad/job/#jobhcl2). Really I'm using it to pass in parameters to a Nomad job (if you're unfamiliar with Nomad it's effectively like passing in variables to ECS/Fargate/Kubernetes)

polite-mechanic-60124

09/28/2021, 7:35 PM

So when the preview output is string, it can't parse the string to get the variables and any required parameters fail

red-match-15116

09/28/2021, 8:32 PM

But it’s never actually a string… during

preview

it’s just not resolved because each item within the Output.all is not known.

red-match-15116

09/28/2021, 8:33 PM

I’m guessing you don’t actually want to pass the parameters during preview though? Right? Only during an actual update?

red-match-15116

09/28/2021, 8:44 PM

Oh wait okay I think I understand. It’s when it’s the first update that

preview

is unknown and in all following updates it is known at preview time. So during the first preview there are no outputs… I’m still not sure you want to be passing this information to another job during

preview

as the outputs are unresolved. You can use

pulumi.runtime.is_dry_run()

to determine whether you are running a preview or not.

red-match-15116

09/28/2021, 8:45 PM

You could choose to export an empty dict when it’s a preview or something along those lines…

polite-mechanic-60124

09/28/2021, 9:50 PM

Got it. Thanks Komal, this was helpful

2 Views

Open in Slack

Previous Next

Pulumi Community

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.