Cannot run pulumi up with resource AWS
See original GitHub issueExpected behavior
- Should run
pulumi up
as expected.
Current behavior
After doing a clean install of pulumi with brew (MacOS 10.15.7) and logged in (as pulumi login --local
) cannot deploy my stack of the project anymore.
Also tried after a clean install of: https://github.com/pulumi/examples/tree/master/aws-ts-static-website with same results.
Steps to reproduce
- Clone https://github.com/pulumi/examples/tree/master/aws-ts-static-website
npm install
pulumi login --local
- Config the stack with
config set
command:
encryptionsalt: XXX
config:
aws:profile: myprofile-super-admin
static-website:pathToWebsiteContents: www
static-website:targetDomain: test.mydomain.com
pulumi up
: which produces the following output:
Previewing update (dev):
Type Name Plan Info
+ pulumi:pulumi:Stack aws-ts-static-website-dev create... /home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.0. + pulumi:pulumi:Stack aws-ts-static-website-dev create... /home/runner/work/pulumi-aws/pulumi-aws/provider/resources.go:4173 +0x52e1 Type Name Plan Info + pulumi:pulumi:Stack aws-ts-static-website-dev create... /home/runner/work/pulumi-aws/pulumi-aws/provider/cmd/pulumi-resource-aws/m + pulumi:pulumi:Stack aws-ts-static-website-dev create 9 messages
└─ pulumi:providers:aws default_4_5_0 1 error
Diagnostics:
pulumi:providers:aws (default_4_5_0):
error: could not read plugin [/Users/me/.pulumi/plugins/resource-aws-v4.5.0/pulumi-resource-aws] stdout: EOF
pulumi:pulumi:Stack (aws-ts-static-website-dev):
panic: strconv.ParseUint: parsing "": invalid syntax
goroutine 1 [running]:
github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tfbridge.GetModuleMajorVersion(0x0, 0x0, 0xc0013bf5b0, 0x1)
/home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.0.0/pkg/tfbridge/info.go:730 +0x1dc
github.com/pulumi/pulumi-aws/provider/v4.Provider(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/home/runner/work/pulumi-aws/pulumi-aws/provider/resources.go:4173 +0x52e1b
main.main()
/home/runner/work/pulumi-aws/pulumi-aws/provider/cmd/pulumi-resource-aws/main.go:26 +0x37
Syncing contents from local disk at /Users/me/Desktop/examples/aws-ts-static-website/www
I have the project up and running just yesterday, and I have tried to uninstall and reinstall pulumi binary with no results. Any clue on this?
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Troubleshooting Guide
This guide covers common troubleshooting techniques when using Pulumi, such as tracing, manually editing deployments, and resolving common errors.
Read more >Destroy fails when AWS resources cannot be found #59
In @clstokes' repo, the fact that pulumi refresh fails due to the cluster being unavailable seems like a separate bug we should open...
Read more >Pulumi AWS Native Provider (preview)
Add the bin folder to your $PATH or copy the bin/pulumi-resource-aws-native file to another location in your $PATH . Running an example.
Read more >My pulumi stack was created with an older plugin version ...
Those resources have a provider attached to them with a specific version of the plugin. ... then you need to run a successful...
Read more >How to Easily Deploy an Amazon EKS Cluster with Pulumi
Pulumi allows you to mix management of Kubernetes resources, AWS ... To get started, sign up at pulumi.com and download the Pulumi Command ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @dferretti and @vanbasten17 the v4.5.1 package is out now so that should work. I’ll leave this issue open so if you can let me know by 👍 this comment that you’re good now and I’ll close it
Ok, so this is controlled through the dependencies in the
package.json
file: