This message was deleted.

sparse-intern-71089

04/20/2021, 2:48 AM

This message was deleted.

green-musician-49057

04/20/2021, 2:53 AM

We're using v3 of the Pulumi SDK. Not sure how we would upgrade to v3 of the Automation SDK, but I think that version is referring to the action itself?

adventurous-garage-59192

04/20/2021, 3:22 AM

Can confirm, just started getting the same issue. Was the action version suppose to be bumped as well? The Pulumi v3 requirement has rolled out to

pulumi/actions@v2

consumers.

green-musician-49057

04/20/2021, 3:27 AM

UPDATE: We fixed this by pinning the version of the pulumi action, e.g.

uses: pulumi/actions@v2.2.0

red-match-15116

04/20/2021, 3:35 AM

Hey folks! It was not intended that this would be pushed to consumers before we did the

v3

release.

red-match-15116

04/20/2021, 3:36 AM

So, just for my own understanding, if you don’t pin the action version it appears it pulls in what’s in the main branch in the action? That’s pretty wild. I would’ve thought it would pull the latest released version.

flaky-ghost-73674

04/20/2021, 3:37 AM

I believe that’s right. Actions generally recommends (and will produce templates that) pin to a specific tag with the

@[tag]

syntax, but if you don’t provide one I think it takes latest from the default branch.

green-musician-49057

04/20/2021, 3:39 AM

For what it's worth, we had it pinned to @v2

red-match-15116

04/20/2021, 3:47 AM

So I think there are 2 issues here: 1. @green-musician-49057 it sounds like you want the action to be

v3

so you can use the

v3

CLI because your code is using automation api from SDK

v3

- is that right? 2. @adventurous-garage-59192 can you tell me more about the issue you’re running into? Are you getting the same error? And you’re using CLI v2?

green-musician-49057

04/20/2021, 3:50 AM

We were not using the automation API, and we were on pulumi sdk

v2.24.1

the first time the issue cropped up, about 3 hours ago, 6:02PM PDT

red-match-15116

04/20/2021, 3:52 AM

Right, but the error says that you’re using CLI v3 - is that true?

Copy code

You are using Pulumi CLI version 3.0.0 with Automation SDK v2. Please update the SDK.

green-musician-49057

04/20/2021, 3:54 AM

we were using whatever is installed from this action:

pulumi/action-install-pulumi-cli@v1.0.1

green-musician-49057

04/20/2021, 3:55 AM

pulumi-version

specified. I assume that would try to install the latest, which would be v3

👍🏽 1

red-match-15116

04/20/2021, 3:55 AM

Yeah, I that action installs

latest

if no version is specified. You can specify the version with:

Copy code

- name: Install pulumi
  uses: pulumi/action-install-pulumi-cli@v1.0.2
  with:
    pulumi-version: 2.25.1

adventurous-garage-59192

04/20/2021, 4:23 AM

Pinning the CLI version fixed the issue, thanks! I guess the problem is in the opposite direction than I assumed, with a new version of the action that supports v3 not being published yet. Will update my pulumi stacks when it is!

billowy-army-68599

04/20/2021, 5:16 AM

hey sorry about this, we have a newly released version of the Pulumi action using the latest major version - it's highly recommended you pin to major versions in any case, but hopefully this should fix your CI pipelines! Sorry for the disruption

7 Views

Open in Slack

Previous Next

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.