-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: pulumi.runtime.invokeOutput is not a function #4641
Comments
pulumi/pulumi#17518 seems to be related to this one |
#4641: TypeError: pulumi.runtime.invokeOutput is not a function invokeOutput was introduced pulumi/pulumi#17237 into the core Node JS SDK v3.133.0 and onward: pulumi/pulumi@f74a5df#diff-f786ce189e2b1bb74d5f9425d102b713287faea09bc04b692ea0d42e1b035a10R95 |
@mausch could you provide a more self-contained repro? I tried running the EKS cluster example in https://github.com/pulumi/pulumi-eks/blob/master/examples/cluster/index.ts#L20 on these versions of Pulumi Core, EKS and AWS and it seems to provision fine. Could something be downgrading the "@pulumi/pulumi" SDK version in your program for some reason? What is in your packages-lock.json or yarn.lock? |
@mausch we ran this down with the team a bit further. AWS v3.55.0 used this minimum core dependency:
https://github.com/pulumi/pulumi-aws/blob/v6.55.0/sdk/nodejs/package.json#L16 And it used this version of Node SDK generator from Pulumi Core that controls the minimum SDK dependency:
This minimum version was too low it seems, which is a bug. This is maintained in this file: It has since been fixed to correctly indicate a higher necessary "@pulumi/pulumi" dependency that includes the new functions such as pulumi.runtime.invokeOutput. It looks though that these fixes have not propagated yet to pulumi-aws. This routine update PR should fix the problem by using the latest version of the Node SDK generator: We are releasing the next minor version of the provider presently and I believe the problem should be fixed. |
Can you reproduce this problem with https://github.com/pulumi/pulumi-aws/releases/tag/v6.56.0 ? |
I believe this should be fixed in the latest release, but please let us know if not so. |
Describe what happened
In Typescript, with @pulumi/eks 2.8.1 and @pulumi/aws 6.55.0 trying to create an EKS cluster crashes with:
Apparently there's been some breaking change in
getPartitionOutput
?See also sst/sst#3880
Sample program
Log output
No response
Affected Resource(s)
No response
Output of
pulumi about
CLI
Version 3.122.0
Go Version go1.22.4
Go Compiler gc
Plugins
KIND NAME VERSION
resource aws 6.55.0
resource aws-native 0.97.0
resource command 0.9.2
resource docker 4.4.5
resource eks 2.8.1
resource kubernetes 4.5.4
language nodejs unknown
resource random 4.14.0
Host
OS nixos
Version 24.05 (Uakari)
Arch x86_64
This project is written in nodejs: executable='/nix/store/ilkfhnqz4xczrliqjva8770x2svbfznd-nodejs-20.14.0/bin/node' version='v20.14.0'
...
Dependencies:
NAME VERSION
@aws-sdk/types 3.609.0
@pulumi/aws 6.55.0
@types/node 14.18.35
aws-sdk 2.1658.0
fast-xml-parser 4.4.1
js-yaml 4.1.0
ts-node 10.9.1
@pulumi/docker 4.4.5
@pulumi/eks 2.8.1
typescript 5.2.2
@types/js-yaml 4.0.8
node-fetch 3.3.2
@pulumi/aws-native 0.97.0
@pulumi/command 0.9.2
@pulumi/kubernetes 4.5.4
@pulumi/random 4.14.0
tmp 0.2.1
Pulumi locates its logs in /tmp/nix-shell.IUphpA by default
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: