-
Notifications
You must be signed in to change notification settings - Fork 73
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
work-dir does not work as a replacement for --cwd #966
Comments
malnor
added
kind/bug
Some behavior is incorrect or out of spec
needs-triage
Needs attention from the triage team
labels
Jun 19, 2023
dixler
added
area/cicd
and removed
needs-triage
Needs attention from the triage team
labels
Jun 26, 2023
dixler
pushed a commit
to pulumi/pulumi
that referenced
this issue
Jun 29, 2023
6 tasks
Hey @malnor, sorry that this issue appears to have gone stale. Is this still affecting you? I'm curious to get more information since with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Running a pipeline trying to use work-dir isn't working as expected. The work-dir directory becomes
Which then fails with
This should happen because it cannot find the stack because it is the wrong folder.
If we set workdir to .../xxx we get
And the error is
Looks like it cannot find pulumi at all?
pulumi --cwd xxx --stack xxx.test
works just find locallyExpected Behavior
work-dir should (from our understanding) work the same way as --cwd in the pulumi-cli
Steps to reproduce
Monorepo with folders for each project
Should work?
Shouldn't work but gives a different error?
Output of
pulumi about
We cannot run it in the action (it is not an allowed command) - so we assume that you mean locally
Running locally from the root (which is not what we really want), we always use --cwd
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: