Hello, I am sorry to report that the “invoke” fix in 1.5.3 is regressing the use of

provider

in the

ConfigFile

. It seems to use the ambient kube provider.

Hi Eron, I responded on the issue. I wasn’t able to reproduce this behavior. Can you open an issue with more details on your setup?

Can you post your example? then I can compare.

To make your example fit, the guestbook would be wrapped in a ComponentResouce.

Testing this now:

export class TestComponentResource extends pulumi.ComponentResource {
    constructor(name: string,
                opts: pulumi.ComponentResourceOptions = {}) {
        super("test:kubernetes-ts:TestComponentResource", name, {}, opts);

        new k8s.yaml.ConfigFile("guestbook",
            {file: "guestbook.yaml"}, {parent: this}
        );
    }
}

new TestComponentResource("test", {provider: gkeCluster.provider});

OK, thanks very much for investigating, I’ll try to make a repro based on your script. One error I noticed in mine is that I didn’t have the

parent

set on the provider; I had

dependsOn

.

Sounds good, thanks