https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
f
Can you 
await
`pulumi.Input`s?
Ultimately, I think this is my issue:
Copy code
Type 'Promise<Output<{ id: string; outs: string; }>>' is not assignable to type 'Promise<CreateResult>'.
I somehow need to work with Pulumi outputs/inputs inside of the 
create
method.
w
You can use 
.get
on your Outputs inside dynamic providers, since they will be run in a separate process. If you have not yet seen this - it’s worth a read - it doesn’t exactly answer this question, but does provide some background to understand why this is true: https://pulumi.io/reference/programming-model/#dynamicproviders
f
Yep, that has been quite helpful! This last bit of navigating input/outputs has proven the hardest.
I receive this message when trying to use `get`:
Copy code
error: Plan apply failed: Cannot call '.get' during update or preview.
    To manipulate the value of this Output, use '.apply' instead.
Example of what I'm trying to do:
Copy code
async create(args: DatomicIonsArgs) {
    const configUri = pulumi.output(args.configUri).get();

    const cliResult = await deployIons({
        projectDirectory: args.projectDirectory,
        configUri: configUri
    }, this);

    console.log(cliResult);

    if (cliResult) {
        return {id: "", outs: ""};
    } else {
        throw new Error("Ion deployment failed.");
    }
}
Somehow the example here https://github.com/pulumi/pulumi/blob/master/examples/dynamic-provider/simple/index.ts uses Inputs in the args. I don't see how that can work.
Somehow it is pulling 
inputs.left
and 
inputs.right
off of 
inputs
in the create method. I believe those are actually going to be 
Input<number>
not 
number
. Unless Pulumi is unwrapping things behind the scenes...
The example isn't very helpful because lots of things are typed with 
any
.
Does Pulumi pass the actual, unwrapped (i.e. non-Output) values of the 
inputs
to the provider methods?
w
Pulumi will indeed have unwrapped any inputs before passing them into the 
create
method, so you should not in general have to deal with outputs here. In particular 
arts.configUri
will be a plain JavaScript object already.
f
I see, makes sense! I think that fixes it.
Open in Slack
PreviousNext
Powered by

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.

Powered by