Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Make pulumi login respect configuration in Pulumi.yaml #1120

Closed
tgummerer opened this issue Feb 9, 2024 · 3 comments · Fixed by #1299
Closed

Make pulumi login respect configuration in Pulumi.yaml #1120

tgummerer opened this issue Feb 9, 2024 · 3 comments · Fixed by #1299
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed

Comments

@tgummerer
Copy link
Contributor

While working on #1081, we noticed that pulumi login wasn't respecting the configuration in Pulumi.yaml, and thus errored out when no cloud-url was given in the action. We should improve pulumi login, so it takes the setting in Pulumi.yaml into account if that file is available to reduce confusion for users.

/xref https://github.com/pulumi/home/issues/3298

@justinvp justinvp added the kind/enhancement Improvements or new features label Feb 12, 2024
@renannprado
Copy link
Contributor

I'm facing the same issue.

Workaround:

- id: prepare
  run: |
    cloudUrl=`cat Pulumi.yaml | yq '.backend.url'`
    echo "cloudUrl=$cloudUrl" >> $GITHUB_OUTPUT

@Frassle Frassle transferred this issue from pulumi/pulumi Mar 13, 2024
@Frassle
Copy link
Member

Frassle commented Mar 13, 2024

OK had a look into this and pulumi login does respect the backend set in the Pulumi.yaml. It looks like the issue is actions isn't running the initial login command in the same directory as all the other commands.

@pulumi-bot
Copy link

This issue has been addressed in PR #1299 and shipped in release v6.0.1.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants