Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pulumi 2.0 roadmap #3591

joeduffy opened this issue Nov 29, 2019 · 2 comments


Copy link

@joeduffy joeduffy commented Nov 29, 2019

This is a tracking issue for the Pulumi 2.0 roadmap. It will be updated as the roadmap shapes up. Please let us know what you think with appropriate emojis and comments. Thank you! 馃挏

Pulumi 2.0 is the next major version of Pulumi. Being a major release, minor breaking changes are possible, however we are striving to avoid that wherever possible. Many of the features of Pulumi 2.0 are being actively developed in "preview" as part of Pulumi 1.x builds, and are targeting general availability as part of Pulumi 2.0. You can continue to work with these new features as part of Pulumi 1.x builds over the coming weeks and months as we finalize the features of Pulumi 2.0.

Here are some of the larger features that are expected to be part of Pulumi 2.0:

We will continue to invest in many smaller issues, including bug fixes, incremental improvements, and new capabilities around existing features, both as part of Pulumi 1.x and included in Pulumi 2.0.

You can share your feedback on areas you'd like to see more investment by commenting here, opening a new issue, or upvoting an existing issue. Community and customer feedback is what drives everything we do at Pulumi, so your feedback is essential to us ensuring a great 2.0 release!

You can also track the milestone roadmap more granularly as it evolves in the Pulumi Roadmap.


This comment has been minimized.

Copy link

@trondhindenes trondhindenes commented Dec 2, 2019

One thing that I find super-disappointing is that SSO is only available at the enterprise level. I don't understand why Pulumi (and many SaaS apps) treat single-sign on as something only the largest organizations want/need. (btw kudos to Datadog and Opsgenie for including sso support in all tiers)

We're only around 40 developers, but we have a policy of only using sso-integrated services (with a few exceptions, but very few), which is a contributing reason we've skipped on Pulumi so far.

Please consider either including sso/saml support on all pricing tiers, or at least offer it as a paid add-on so that it can be activated on all tiers. It would allow us to at least test out Pulumi in a few projects.


This comment has been minimized.

Copy link

@LouisAmon LouisAmon commented Dec 3, 2019

For me a critical feature would be to be able to develop my own providers in any language.
Dynamic Providers are nice but they aren't a stable solution. I haven't been able to find any example of e.g. a Python provider.

I'm willing to put money on it and hire people to develop open-source providers for 3rd parties (e.g. Stripe, Snowflake, etc.) without going through Terraform and its terrible Golang & custom DSL.

Regardless, good job to the Pulumi team so far, you're doing great 馃憤

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can鈥檛 perform that action at this time.