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

hmm, I think the only way is to separate this into its own project, or use a config flag on the stack to enable it

I’m trying to add a new resource to a stack. I want to run `pulumi up` to add it to the stack, but I don’t want pulumi to update other resources as part of (e.g. helm charts that would be updated)

Have you made any code changes? It should only update if your code for the helm chart has changed 

the helm chart has changed. `pulumi up` shows a bunch of things that would be updated. I don’t want to update them yet - I only want to create the new resource that I added to my pulumi config

<@U01C549817F> - this was a good question, I didn't know the answer. It turns out, urns are predictable, so you can still use `-t`

i grabbed the urn of the resource being created using `jq` but you can probably just run `pulumi preview` and copy it

```pulumi preview -j | jq '.steps[] | select(.op=="create") | .urn'```
and then run `pulumi up -t &lt;urn&gt;`

here's a quick demo:
<https://asciinema.org/a/8ryIYrUzm080ZyW2pcFLx3AO6>

ah, cool. `pulumi preview` doesn’t provide an urn (anywhere that I can see) but `-j` does