Supporting filtering resources to be applied in YAML, Kustomize, Chart resources.

[AaronFriel]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Using Transformations and a workaround for the following feature request, it's possible to filter the resources. This is however, a bit clumbsy.

• Allow tranformations to omit or filter #486

It's a very common pattern when deploying large manifests that we need to deploy some resources before others or filter resources. For example, I might want to deploy all CRDs and namespaces first in one Pulumi resource, then deploy all of their dependencies via a second.

With the upcoming release of yaml/v2.ConfigFile and yaml/v2.ConfigGroup, the following workaround won't work.

Current behavior

Here's an example of how I use this to filter the CRDs, to apply them first:

const crds = new k8s.kustomize.Directory(
  `${name}-crds`,
  {
    directory: './kubeflow', // relative to Pulumi project root
    transformations: [crdsOnly, skipAwait, patchForce],
  },
  { ...opts, retainOnDelete: true },
);

export function crdsOnly(obj: any, opts: pulumi.CustomResourceOptions): void {
  if (typeof obj === 'object' && obj !== null) {
    if (!objIsCrd(obj)) {
      removeItem(obj);
    }
  }
}

function objIsCrd(obj: object): boolean {
  return 'kind' in obj && obj.kind === 'CustomResourceDefinition';
}

// Workaround for Pulumi, this effectively removes it from the resources to apply
function removeItem(obj: any): void {
  for (const key of Object.keys(obj)) {
    if (key !== 'apiVersion' && key !== 'kind') {
      // eslint-disable-next-line @typescript-eslint/no-dynamic-delete
      delete obj[key];
    }
  }
  obj.apiVersion = 'v1';
  obj.kind = 'List';
  obj.items = [];
}

Affected area/feature