-
Notifications
You must be signed in to change notification settings - Fork 53
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
Unable to add a plugin to a stack #542
Labels
impact/accessibility
Something that is difficult or impossible for some people to use
kind/enhancement
Improvements or new features
Comments
thanks for reporting this @avijitsarkar123. I think we're intentionally isolating the stack root directories to avoid cross contamination, but I can see how that makes configuring custom plugins difficult. We'll hang on to this issue as a reminder to design a way to do this better. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
impact/accessibility
Something that is difficult or impossible for some people to use
kind/enhancement
Improvements or new features
What happened?
I want to add a pulumi plugin for my stack, currently the
pulumi-kubernetes-operator
pod creates the pulumi workdir here, as its a dynamic path so I have no pay to run apulumi plugin install
from a local file that I am adding to the docker image for the stack to pickup.Example
I added below to the Dockerfile to have my plugin installed
It is installing the plugin in the path
/home/pulumi-kubernetes-operator/.pulumi/plugins/
but the Stack root dir is/tmp/pulumi-working/[my-namespace]/[my-stack-name]-[random alphanumeric string]/.pulumi
so the custom plugin that I installed isn't being used by the stack when its doingpulumi up
internally and I am getting the below error:Output of
pulumi about
Additional context
My objective is to have a custom plugin available to my Stack, I am trying to achieve it by adding the
pulumi plugin install...
cmd to the Dockerfile assuming it will be used by the Stack but thats not happening as the pulumi root for the stack is different and my Dockerfilepulumi plugin install
doesn't apply to that pulumi rootdir.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: