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

<https://www.pulumi.com/docs/reference/pkg/kubernetes/kustomize/directory/#kustomize-directory-with-transformations>

thanks <@U02GR5R9SE9>, I’m familiar with kustomize, but as far as I understand kustomizations are still “static” in nature. What I need is editing a k8s resource based on output of another aws resource. for example, a deployment that accepts the vpc cidr as a flag.

I would need to use `Apply` inside the transformation. The transformation docs state `any values set on the state must be prompt (not Output values)`

Well, we just hung the thread till we had the values we wanted.

But we're getting rid of the transform in favour of this in the near term: <https://fluxcd.io/docs/components/kustomize/kustomization/#variable-substitution>

So we'll just spit out a secret this can consume.

What do you mean by `we just hung the thread till we had the values we wanted.`? How do you technically do that? and how does it affect the previews using `pulumi up`?

The flux variables approach is interesting, thanks

One downside is that your gitops repo is getting another step further from the actual resources deployed in the cluster

```            while (Deployment.Instance.IsDryRun != true &amp;&amp; string.IsNullOrEmpty(resourceGroupNameOutputValue))
            {
                Thread.Sleep(200);
            }```

For me pulumi is about getting cloud resources up then handing over to flux.