This message was deleted.
# awss
sparse-intern-71089
07/13/2021, 9:12 PMThis message was deleted.
b
billowy-army-68599
07/13/2021, 9:13 PM
are you running an
npm installp
purple-orange-91853
07/13/2021, 9:14 PMno I'm not. If it change the version of the plugin to match the version defined in the error it will work
b
billowy-army-68599
07/13/2021, 9:15 PM
the npm install should install the right versions
p
purple-orange-91853
07/13/2021, 9:16 PMI take back I am doing a
yarn installpurple-orange-91853
07/13/2021, 9:19 PMfor testing I added another yarn install before the pulumi up step and got the same message back.
purple-orange-91853
07/13/2021, 9:24 PM Copy code
------------------------------
Executing command: pulumi login
Logging in using access token from PULUMI_ACCESS_TOKEN
Logged in to <http://pulumi.com|pulumi.com> as jakeatomic (<https://app.pulumi.com/jakeatomic>)
------------------------------
Executing command: pulumi plugin install resource aws v4.11.0
[resource plugin aws-4.11.0] installing
Downloading plugin: 75.91 MiB / 75.91 MiB 100.00% 1s
------------------------------
Executing command: pulumi plugin install resource kubernetes v3.5.0
[resource plugin kubernetes-3.5.0] installing
Downloading plugin: 26.22 MiB / 26.22 MiB 100.00% 0s
------------------------------
Executing command: pulumi plugin install resource eks v0.22.0
[resource plugin eks-0.22.0] installing
Downloading plugin: 670.75 KiB / 670.75 KiB 100.00% 0s
------------------------------
Executing command: pulumi plugin ls
NAME KIND VERSION SIZE INSTALLED LAST USED
aws resource 4.11.0 271 MB n/a 12 seconds ago
aws resource 3.38.1 254 MB n/a 2 seconds ago
eks resource 0.22.0 158 MB n/a 9 seconds ago
kubernetes resource 3.5.0 67 MB n/a 10 seconds ago
kubernetes resource 2.9.1 77 MB n/a 1 second ago
+ pulumi:pulumi:Stack platform-staging create
pulumi:providers:aws default_4_12_0 error: no resource plugin 'aws-v4.12.0' found in the workspace or on your $PATH, install the plugin using `pulumi plugin
install resource aws v4.12.0`
+ pulumi:pulumi:Stack platform-staging create
pulumi:providers:aws default_4_12_0 1 errorb
billowy-army-68599
07/13/2021, 9:29 PM
i'm checking it automatic plugin acquisition works for yarn, you shouldn't need to install the plugins manually like this
billowy-army-68599
07/13/2021, 9:30 PM
to answer your original question, you can pull the latest release from the github release if you'd like
billowy-army-68599
07/13/2021, 9:32 PM
Copy code
pulumi plugin install resource aws $(curl -s <https://api.github.com/repos/pulumi/pulumi-aws/releases/latest> | jq '.tag_name' -r)p
purple-orange-91853
07/13/2021, 9:32 PMthank you. For some context this is what the commands in our deployment step looks like
Copy code
commands:
- pulumi login
- pulumi plugin install resource aws v4.11.0
- pulumi plugin install resource kubernetes v3.5.0
- pulumi plugin install resource eks v0.22.0
- pulumi plugin ls
- pulumi stack select atomicfi/${{STAGE}}
- pulumi stack
- pulumi up --non-interactive --yes -rb
billowy-army-68599
07/13/2021, 9:32 PM
where is your
yarn installp
purple-orange-91853
07/13/2021, 9:33 PMThis is the current entire pipeline config. The yarn install is done during the container build step.
Copy code
# More examples of Codefresh YAML can be found at
# <https://codefresh.io/docs/docs/yaml-examples/examples/>
version: "1.0"
# Stages can help you organize your steps in stages
stages:
- "clone"
- "build"
- "deploy"
steps:
clone:
title: "Cloning repository"
type: "git-clone"
repo: "atomicfi/platform"
revision: "${{CF_BRANCH}}"
git: "github"
stage: "clone"
build:
title: "Building Docker image"
image: pulumi/pulumi
working_directory: "${{clone}}"
tag: "${{CF_BRANCH_TAG_NORMALIZED}}"
commands:
- yarn install
stage: "build"
RunPulumi:
title: Deploying
stage: deploy
working_directory: "${{clone}}/deployments/aws-${{AWS_REGION}}"
image: pulumi/pulumi:v3.6.1
kube_context: ${{STAGE}}
buildkit: true
ssh: default
commands:
- pulumi login
- pulumi plugin install resource aws v4.11.0
- pulumi plugin install resource kubernetes v3.5.0
- pulumi plugin install resource eks v0.22.0
- pulumi plugin ls
- pulumi stack select atomicfi/${{STAGE}}
- pulumi stack
- pulumi up --non-interactive --yes -r
# - pulumi destroy --non-interactive --yes -rpurple-orange-91853
07/13/2021, 9:34 PMand to note and make clear, if I change the line for the aws resource plugin to match the version in the error it will work
purple-orange-91853
07/13/2021, 9:35 PMwhich is where I'm stumbling as it will work one day, then not again the next until the version is manually updated in this config file
b
billowy-army-68599
07/13/2021, 9:35 PM
so your provider version is stored in 2 places:
- your
package.jsonbillowy-army-68599
07/13/2021, 9:36 PM
so if you have a liberal constraint in your
package.jsonyarn installpulumi stack exportbillowy-army-68599
07/13/2021, 9:36 PM
you might want to have a more strict constraint in your
package.jsonbillowy-army-68599
07/13/2021, 9:37 PM
can you share your
package.jsonp
purple-orange-91853
07/13/2021, 9:37 PM Copy code
{
"dependencies": {
"@pulumi/aws": "^4.8.0",
"@pulumi/awsx": "^0.30.0",
"@pulumi/eks": "^0.31.0",
"@pulumi/kubernetes": "^3.3.1",
"@pulumi/pulumi": "^3.4.0",
"codefresh": "^0.75.26",
"js-yaml": "^3.14.1",
"lodash": "^4.17.21"
},
"devDependencies": {
"@types/node": "^15.12.2"
}
}b
billowy-army-68599
07/13/2021, 9:38 PM
yeah, so you're getting any version higher than 4.8.0, I'd probably pin that to a specific version honestly, unless you're ready to update
p
purple-orange-91853
07/13/2021, 9:39 PMOk, let me try that
purple-orange-91853
07/13/2021, 9:43 PMok, that seemed to work
purple-orange-91853
07/13/2021, 9:43 PMI'm getting a new error now, but that is completely unrelated to this as it seems to be some bad code in the actual ts files
purple-orange-91853
07/13/2021, 9:46 PMthanks for the help!