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

if i make a kubernetes namespace, and then want to use that namespace later on resources, is there a way to make it show up in the diff on the resources? it just appears as `output&lt;string&gt;`, even though the namespace resource shows the actual string

it needs to know name upfront, instead of using namespace resource name, use same input for both namespace and resources in that namespace and use ` {dependsOn: []} option for resources to enforce order

so instead of (pseudocode):

```
const name = "x";
const ns = new k8s.Namespace(name)
const cfg = new k8s.Configmap("abc", { namespace: ns.name })
```

do
```
const name = "x";
const ns = new k8s.Namespace(name)
const cfg = new k8s.Configmap("abc", { namespace: name }, {dependsOn: [ns]})
```

unfortunately, can't do that because of pulumi's name mangling

i.e. the namespace isn't actually `name`, it's e.g. `name-tld6bkwm`

try  `new k8s.Namespace(name, { name: name })`

usually it forces name of a resource you want

do you mean as the second or third argument?

<@UM6PHB1RS> You should be able to reference the ns `.metadata.name`

<@UE1LN7A22> that's what i'm doing, but it appears as `output&lt;string&gt;` in the preview/diff

Would you mind opening an issue about that? We’ve been working on some changes to diff behavior lately, and that could be a regression.

<https://github.com/pulumi/pulumi-kubernetes/issues/new>

<@UG53R9UJC> i guess you mean to use `{metadata: {name: name}}` since that's what's accepted by the type. which, interestingly, does then show the actual output in the diff, even when using `namespaceResource.metadata.name`