Today we published our Pulumi 2.0 roadmap! We aim to GA this in H1 2020, and it will include a lot of goodies based on your feedback • "CrossGuard", our new policy as code framework • Finishing Go and .NET languages • Enabling libraries like Crosswalk to go multi-language • Improved productivity with tools like watch mode • Comprehensive infrastructure testing support • Self-hosting and on-prem support for the Pulumi service • Much more, based on your feedback Several key features are already available in preview -- including CrossGuard starting today -- so please check them out and let us know what you think. (When in doubt, set

PULUMI_EXPERIMENTAL=true

to enable.) Read more here https://www.pulumi.com/blog/pulumi-2-0-roadmap/ and please upvote, open issues, or comment on the roadmap directly here: https://github.com/pulumi/pulumi/issues/3591. Thanks for your continued support!

Hi @big-piano-35669, Thanks to share the roadmap. In the company I’m working for, they were comparing the pulumi and the terraform providers. And to not be able to use any terraform provider seems to be annoying for us (even if they will certainly not use them). It could be great if pulumi can provide a way to integrate easily with existing terraform ecosystem without having to write bridge in go (if the bridge can be generated, it was fine 😉 ) Here is a small feedback for 2.0

Thanks, Manuel. Appreciate the feedback. We've had some ideas on how to dynamically leverage a single, shared Go binary, and we will definitely take note of this and consider it in our planning. /cc @microscopic-florist-22719 @broad-dog-22463 @stocky-spoon-28903

currently, there is no specific need. But I note that I can ask for it 😉 thanks

Even if we were to have the single Go binary, some element of mapping will always be required to generate language bindings. That said, the level of effort to bring any TF provider to Pulumi is dramatically smaller than the gains that general purpose programming languages give.

For roadmap 2.0, I would add the ability to move/transfer a stack from a backend to another https://github.com/pulumi/pulumi/issues/3683. I think it can help companies to use free pulumi backend service first and may be move to a paying service later. Otherwise, if they use a cloud storage account, they will probably not consider using a paying service later.

Thanks for opening the issue on that @boundless-airport-99052 - it's not the first time I have heard of this being a requirement