Any ideas why I can t use this inside automation api process

Question

Any ideas why I can t use this inside automation api process ```const config = await authorization getClientConfig const token = await authorization getClientToken ``` Getting ```creating error Program run without the Pulumi engine available re run using the `pulumi` CLI```

bored-oyster-3147 · Answer

Your error looks unrelated Do you have the Pulumi CLI installed Automation API currently depends on the CLI still

icy-jordan-58549 · Answer

yep it s installed btw I have tested this inside automation api in another script and it does work

icy-jordan-58549 · Answer

probably something wrong with my CustomProvider

bored-oyster-3147 · Answer

Will probably need more information in order to help then

lemon-agent-27707 · Answer

Are you trying to call this code from within your pulumiFunction or just in the general automation script

icy-jordan-58549 · Answer

I ve decided to test it inside general automation script automation api and it does work < lemon agent 27707>

icy-jordan-58549 · Answer

but it was not working when I ve embedded it inside CustomResource

icy-jordan-58549 · Answer

something like this <https github com pulumi examples blob master classic azure ts dynamicresource cdnCustomDomain ts>

icy-jordan-58549 · Answer

but here you are using ```let clientID = azure config clientId let clientSecret = azure config clientSecret let tenantID = azure config tenantId let subscriptionID = azure config subscriptionId ```

icy-jordan-58549 · Answer

instead of ```const config = await authorization getClientConfig const token = await authorization getClientToken ```

icy-jordan-58549 · Answer

does it make sense < bored oyster 3147> < lemon agent 27707>

bored-oyster-3147 · Answer

AFAIK you don t want to `await` inside a pulumi program Automation API can do this but you ll see weird behavior doing that using the CLI with a local program I think What is `authorization` in this context

icy-jordan-58549 · Answer

icy-jordan-58549 · Answer

yep I know I am doing await inside Automation API

icy-jordan-58549 · Answer

btw in the example below you have await inside regular pulumi program wink

bored-oyster-3147 · Answer

Actually there is an important distinction to be made In the examples you linked you are correct that the functions `getAuthorizationManagementClient` and `getRoleIdByName` each contain a couple `await`s But it s important to note that when the pulumi program executes them it does so by piping the resulting `Promise` to a `pulumi output ` call <https github com pulumi examples blob 35caae8d73c3ecb0eac1256ba0e03775f24514da azure ts call azure sdk index ts L48|here > So the pulumi program is dealing with asynchronous actions only through `Output lt T gt ` and is not awaiting the `Promise` explicitly

bored-oyster-3147 · Answer

Also note that <https github com pulumi examples blob 35caae8d73c3ecb0eac1256ba0e03775f24514da azure ts call azure sdk index ts L53|in this line> it is passing the `Promise lt T gt ` to a `Pulumi Resource` directly because `Promise lt T gt ` can be implicitly cast to `Input lt T gt ` again not being awaited explicitly

bored-oyster-3147 · Answer

But to clarify though your `await`s are located inside your dynamic provider implementation and not in your pulumi program Because that should be OK

icy-jordan-58549 · Answer

yeah it s located inside dynamicprovider but currently I ve decided to not go with that approach Anyway thanks for great explanation < bored oyster 3147>

icy-jordan-58549 · Answer

I appreciate that