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 currently, issue tracking it at <https://github.com/pulumi/pulumi/issues/11657> if you want to upvote

Note that targeted updates are frequently used for similar use cases. Via the `—target` flag on the CLI: <https://www.pulumi.com/docs/reference/cli/pulumi_up/|https://www.pulumi.com/docs/reference/cli/pulumi_up/>. 

The issue linked above notes a somewhat specific use case where you might need tainting specifically, but for the majority of use cases we typically find targeted updates can be a better solution. But depends on the specific need. 

Maybe I'm thinking about something else but I guess it depends on what the actual use case for `taint` is.
When I need to replace a resource, with terraform it's
terraform taint xx -&gt; terraform plan -&gt; terraform apply
With Pulumi it's
`pulumi up --replace urn:xx`

taints in ci/cd are something different as per the issue above.