[aws-eks] Cannot call applyRemovalPolicy on KubernetesManifest objects

[otterley]

In an attempt to prevent a Kubernetes resource from being deleted during stack destruction, I tried to use the current tribal-knowledge method:

      const meshResource = cluster.addManifest(`Mesh${clusterName}`, {
        apiVersion: "appmesh.k8s.aws/v1beta2",
        kind: "Mesh",
        metadata: {
          name: "mesh",
        },
        spec: {
          awsName: mesh.meshName,
          namespaceSelector: {
            matchLabels: {
              mesh: mesh.meshName,
            },
          },
        },
      });
      meshResource.node.addDependency(mesh, appMeshController);
      (meshResource.node.defaultChild as cdk.CfnResource).applyRemovalPolicy(cdk.RemovalPolicy.RETAIN);

This did not work:

$ npm run cdk synth       
...
meshResource.node.defaultChild.applyRemovalPolicy is not a function
Subprocess exited with error 1

Environment

• CLI Version : 1.60.0
• Framework Version: 1.60.0
• Node.js Version: 12.18.2
• OS : MacOS Catalina
• Language (Version): TypeScript

---

This is 🐛 Bug Report

[otterley]

Interestingly, it also appears that addPropertyOverride doesn't work either:

(meshResource.node.defaultChild as cdk.CfnResource).addPropertyOverride('UpdateReplacePolicy', 'Retain');
(meshResource.node.defaultChild as cdk.CfnResource).addPropertyOverride('DeletionPolicy', 'Retain');

$ npm run cdk synth       

meshResource.node.defaultChild.addPropertyOverride is not a function

[iliapolo]

The defaultChild of KubernetesManifest resources is not setup to retrieve the underlying cdk.CfnResource, but rather returns a core.CustomResource construct.

Workaround:

(meshResource.node.defaultChild?.node.defaultChild as cdk.CfnResource).addPropertyOverride(...)

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.