Not really… We don’t not have active “cross-cloud” solutions (except things like Kubernetes), resources are defined in terms that are specific to each cloud (S3 / Azure Storage, not “Storage”). Migration may be easier because it’s the same tool that you use, but the program is going to be different.
You can’t make circular dependencies by design. To depend B on A, you need to define A in your program before B, which is not possible.
Great question! Pulumi has a built-in concept of secrets that I believe doesn’t exist anywhere else on this level. So, you can mark any value in your program as secret, and it will never be printing plain-text or stored unencrypted, while still flowing through the program. Also, you can store your secrets in Azure KeyVault etc. and use them in your programs. Examples: https://www.pulumi.com/blog/peace-of-mind-with-cloud-secret-providers/ https://www.pulumi.com/blog/managing-secrets-with-pulumi/ https://www.pulumi.com/blog/7-ways-to-deal-with-application-secrets-in-azure/ (edited)
There’s a Pulumi task in Azure Pipelines that deploys your Pulumi programs. https://www.pulumi.com/docs/guides/continuous-delivery/azure-devops/
We discussed this (and other scripting) but there are no active plans. It would be awesome if you could file at issue for this in https://github.com/pulumi/pulumi
See https://www.pulumi.com/docs/intro/vs/cloud_template_transpilers/ (edited)
Yes, even from the same program. It’s called Explicit Provider Configuration where you define provider as another resource and then pass it in the options while defining other resources.
I don’t know TF licensing that much… I guess similar? Pulumi: CLI and all providers are free for any usage. Everything that I showed you can do for free. Backend SaaS is free for individuals If you want to use our backend SaaS, it’s paid for teams per user per month If you want to deploy our backend at your company, it’s an enterprise agreement
🎉
More questions? https://twitter.com/MikhailShilkov