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

No, we do not currently have a search capability. (But I can confirm it is on our backlog!) Is there a particular scenario you are trying to do here? There might be some way to automate your query using the Pulumi REST API (undocumented, but I can help you get set up).

At some point a change we made to our instance class was reverted, and I was hoping to find what commit was responsible as we didn’t notice for a few days.

The thing that made this change special, is that the modification gets queued up for the next rds instance maintenance window, so it was undetected for a while.

<@U013Q0AKUCW> gotcha. Depending on how active your stack has been, there is an undocumented feature of the Pulumi Console that might help you out. If you navigate to the particular resource in the UI, you will arrive at a link like:

<https://app.pulumi.com/pulumi/static-website/static-website-chris/resources/latest/urn:pulumi:static-website-chris::static-website::aws:s3/bucket:Bucket::requestLogs>

Notice how part of the URL is `/resources/latest/&lt;resource-urn&gt;`. You can change “latest” to whatever the stack version is. So for example, if the latest stack version is “104" then you could change the URL to be `/resources/100/&lt;resource-urn&gt;` and it would load the resources for the 100th update. It would be a little tedious, but you could use that to manually use a git-bisect like approach to find the particular stack update that changed the particular resource property