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

I'm very excited to see <https://github.com/pulumi/pulumi/commit/9374c374c3d3a96fc2ae1e715da511b4125b6628>
Are nightly or prerelease packages available somewhere?

Yes - since this feature is only in the `@pulumi/Pulumi` package, you can just depend on the `”dev”` tag of that package to pull this in. 

You can see the tests in that PR for some examples of how this can be used - docs for this coming soon before this goes out in the next release. 

Note that the last example is actually explicitly motivated by your scenario of injecting dependencies between children of a Helm/YAML deployment. 

Awesome! I'll let you know if I have any problems.

Am I able to use a transformation to completely remove a resource?

e.g. the prometheus operator helm template has some test resources that should be triggered by a hook, but they always fail since I think this needs tiller, so I need to remove them.

Given `obj.metadata.name === "po-grafana-test"`

Otherwise `pulumi up` always fails after timing out

&gt; Am I able to use a transformation to completely remove a resource?

Currently no - and it’s a little more complex to support this cleanly - but it’s something we can look at adding. I do recall that this was useful for the helm chart transformations feature. 