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

to be clear, let’s say I have a file named `test.yaml`; it defines resources `foo` and `bar`, and I want to apply it to clusterA and clusterB.

even if I do:
```new k8s.yaml.ConfigFile(
  "clusterA-res",
  { file: "test.yaml" },
  { provider: clusterAProvider }
);
new k8s.yaml.ConfigFile(
  "clusterB-res",
  { file: "test.yaml" },
  { provider: clusterBProvider }
);```
pulumi still wants to create two resources named `foo` and two named `bar`, so it fails.

Of course, I could create copies of `test.yaml` and rename everything, but that’s obviously undesirable.

Using a transformation like this didn’t work either:
```new k8s.yaml.ConfigFile(
  "clusterA-res",
  { file: "test.yaml" },
  {
    provider: clusterAProvider,
    transformations: [(obj: any) =&gt; {
      obj.name = `clusterA-${obj.name}`;
      return obj;
    }],
  }
);```
pulumi seems to ignore the renaming