https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
b
the plugins are related to the SDK you're using, so unfortunately not.
can you tell me a little bit more about why you want to avoid it?
maybe we can figure something out
b
The idea is pretty simple, I'm working with at least 5 persons, and we want to have the same result when we run pulumi. To be able to achieve that, we now execute it through the runner, where we lock modules and plugins to specific versions. It's inconvenient, and as an engineer, I just want a working tool and not dependency management...
Maybe I just need a little bit more expirience with Pulumi)
b
I see. Generally we leave this to the package manager for your chosen language SDK. We do automatic plugin acquisition from that SDK version, so if you 
npm install @pulumi/aws
and you've set up your dependencies correctly, you should always get the same plugin version
ultimately this is the purvue of the language you've chosen, they all have different dependency management stories
b
Thank you for the answer! I'll try to test it, maybe we are over-engineering here.
b
it may be I'm misunderstanding, if you want to rubber duck it a little happy to hop on a call to discuss, dm me!
b
@billowy-army-68599 Thank you for your support! I really appreciate it. I just need time to work on it and figure out things. In case I would be totally stuck I'll dm you. Thank you again!
2 Views
Open in Slack
PreviousNext
Powered by

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.

Powered by