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.

Pulumi Community

Not strictly a contribution question but probably only something that a contributor would know… is there schema for the plan file? I want to have a crack at writing a workaround for <https://github.com/pulumi/pulumi/issues/13091> whereby I register a transformation that uses the plan to only transform the resources that have changed. Doesn’t look too complicated but I’m entirely sure what all the possible values are for the `steps` field.

I’m guessing it is these? <https://github.com/pulumi/pulumi/blob/master/sdk/go/common/apitype/history.go#L66C1-L97C2>

There's no schema for this, just the Go code. Same as the pulumi state file. It's on our todo list to find a good way to schematise these but not a very high priority I'm afraid.

No worries. I found the manifest in this JSON schema (<https://github.com/pulumi/pulumi/blob/master/sdk/go/common/apitype/deployments.json>) so that helped a bit. I ended up creating a similar JSON schema for the plan. I’m assuming that it shouldn’t change so long as the version in the manifest is 3.x?

might have additions, but no major changes if the version matches