config.Yaml invokes decode but doesn't propagate provider

[rawkode]

Hello!

• Vote on this issue by adding a 👍 reaction
• To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details

When the default Kubernetes provider is disabled, we cannot use yaml.ConfigFile. It seems that an invoke to yaml::decode is made without propagation of the provider.

Error: Invoke: Default provider for 'kubernetes' disabled. 'kubernetes:yaml:decode' must use an explicit provider

Steps to reproduce

    args.provider.urn.apply((u) => console.log(`Provider URN: ${u}`));

    const crds = new kubernetes.yaml.ConfigFile(
      `${this.name}-crds`,
      { file: this.crdsUrl.replace("${VERSION}", this.version) },
      {
        parent: this,
        provider: args.provider,
        dependsOn: args.dependsOn,
      }
    );

This code fails, even though the URN for my provider is correct.

[protometa]

Having same issue with helm.v3.Chart with error

Error: Invoke: Default provider for 'kubernetes' disabled. 'kubernetes:helm:template' must use an explicit provider.

[protometa]

Looks like fix is #1919?

[KaoruDev]

I updated to 3.18.2 and it appears the bug is still present

[omninonsense]

It seems like anything under k8s.kustomize/k8s.yaml/similar fails when the default kubernetes provider is disabled, even when you pass in opts.provider.

[KaoruDev]

hey @lblackstone I just pulled down version 3.19.4 and still am observing the same behavior ☹️

[viveklak]

@KaoruDev are you able to pulumi stack export and make sure the provider for the resource is actually set to v3.19.4 and not using an older version?

[KaoruDev]

Is this the right place to find the version?

The provider field itself didn't have the version. If so, I am misunderstanding how providers work. It looks like I need to recreate the resource in order to pick up the provider changes, is that correct? 😅

[rosskevin]

I'm raising a brand new stack (pre-existing code that previously worked, we are doing a major upgrade) and I ran into this issue. I did just switch to explicit providers in the major update, but it appears that a parented ConfigFile is not receiving the provider. Below is abbreviated for clarity:

Error: Invoke: Default provider for 'kubernetes' disabled. 'kubernetes:yaml:decode' must use an explicit provider.

Invocation:

export const certManager = new CertManager(
  {
    kind: 'ClusterIssuer',
  },
  { providers: { kubernetes, gcp } },
)

Component definition:

import * as k8s from '@pulumi/kubernetes'

export class CertManager extends ComponentResource {
  public readonly version = '1.8.2'
  constructor(args: CertManagerArgs, opts: ComponentResourceOptions) {
    super('af:pulumi:cert-manager:CertManager', 'cert-manager', {}, opts)
    
    const certManager = new k8s.yaml.ConfigFile(
      `https://github.com/cert-manager/cert-manager/releases/download/v${this.version}/cert-manager.yaml`,
      undefined,
      { parent: this },
    )
}

Note that I tried this with both provider and providers args, with the same result. @lblackstone please reopen.

[rosskevin]

...and is there a workaround to pass the providers explicitly inside my ComponentResource?

[viveklak]

@rosskevin you would need to pass the opts to ConfigFile. However, I believe you might run into pulumi/pulumi#9996. Instead you might want to pass the kubernetes provider directly as ConfigFile's provider resource option.

[robertvanhoesel]

I'm getting this exact runtime error while using https://github.com/pulumi/pulumi-kubernetes-cert-manager . Is that package updated correctly?

[EronWright]

Reopening this to cover the remaining cases in NodeJS SDK, e.g. when using providers as opposed to provider.