However, I would group the content directly under that page by IaC tool. Conversion and import are, in my mind, both part of the same customer problem: "We are doing things with X today, and we want to adopt Pulumi. What are our options?" I would group the content by IaC tool, something like:
Note: cf2pulumi is experimental and we have no plans to continue development on it, so we should not be presenting it as a viable option. It cannot convert basic foundational resources. This should be mentioned in our docs.
Kubernetes Manifests
kube2pulumi and crd2pulumi (convert)
YAML output (coexist)
ARM/Bicep (never used this, but would at least include arm2pulumi if it's a viable option and we plan to continue supporting)
ClickOps/Manual Creation (i.e. stuff created in the console via stuff like boto3, talk about pulumi import on a resource, or in bulk here). I have some blog posts/code bases that could be "graduated" to guides for bulk import:
Note that in Migrating from other solutions to Pulumi (which would go away in this proposed change), we talk about migrating "from AWS/Azure/K8s to Pulumi", which is inaccurate. We're actually talking about migrating from CloudFormation/ARM/K8s Manifests, i.e. the single-platform IaC tools, not the platforms themselves.
I've completed the training module and have a significant amount of source material that should be helpful for anyone who ends up working on this. Please reach out.
Existing pages that should be examined as part of this effort:
jkodroff
commented
6 months ago
Hello!
Issue details
I'm working on training/workshop materials on conversion to Pulumi and was finding some gaps in the current documentation.
Our top page is pretty good: https://www.pulumi.com/docs/using-pulumi/adopting-pulumi/
However, I would group the content directly under that page by IaC tool. Conversion and import are, in my mind, both part of the same customer problem: "We are doing things with X today, and we want to adopt Pulumi. What are our options?" I would group the content by IaC tool, something like:
pulumi importon a resource, or in bulk here). I have some blog posts/code bases that could be "graduated" to guides for bulk import:Note that in Migrating from other solutions to Pulumi (which would go away in this proposed change), we talk about migrating "from AWS/Azure/K8s to Pulumi", which is inaccurate. We're actually talking about migrating from CloudFormation/ARM/K8s Manifests, i.e. the single-platform IaC tools, not the platforms themselves.
Be sure to explain https://github.com/pulumi/pulumi/issues/15212 in the guide if it's still an issue at the time we tackle this issue.
I've completed the training module and have a significant amount of source material that should be helpful for anyone who ends up working on this. Please reach out.
Existing pages that should be examined as part of this effort:
Affected area/feature