feat: force options on apply

[cmwylie19]

Description

@lucasrod16 discovered a bug in Pepr when trying to apply a secret that was initially created by Zarf:

  try {
    await K8s(kind.Secret).Apply({
      metadata: {
        name: secretName,
        namespace: ns,
      },
      data: {
        data: secret.data.data,
      },
    });
  } catch (err) {
    Log.error(
      `Error: Failed to update package secret '${secretName}' in namespace '${ns}'`,
    );
  }

The error had to do with a FieldManagerConflict:

"Apply failed with 1 conflict: conflict with \\\"zarf\\\" using v1: .data.data\",\"reason\":\"Conflict\",\"details\":{\"causes\":[{\"reason\":\"FieldManagerConflict\",\"message\":\"conflict with \\\"zarf\\\" using v1\",\"field\":\".data.data\"}]},\"code\":409},\"ok\":false,\"status\":409,\"statusText\":\"Conflict\"}"}

There should be more options exposed in the future but this initial patch it to unblock @lucasrod16 .

Related Issue

Fixes #9

Relates to #

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[lucasrod16]

@cmwylie19 @jeff-mccoy I have a workaround to this problem.

Clearing/stripping the managedFields field from the object and updating the data.data field in the same Patch() operation allows Pepr to take ownership of that field and resolves the field manager conflict error.

https://kubernetes.io/docs/reference/using-api/server-side-apply/#clearing-managedfields

// Clear managedFields to allow Pepr to take ownership of the secret data.data field and update webhook status
// For more information on clearing managedFields to take ownership of an object's field(s): https://kubernetes.io/docs/reference/using-api/server-side-apply/#clearing-managedfields
// TODO: Update to use Server-Side force apply when available in Pepr: https://github.com/defenseunicorns/kubernetes-fluent-client/issues/9
const patchOps: Operation[] = [
  { op: "replace", path: "/metadata/managedFields", value: [{}] },
  { op: "replace", path: "/data/data", value: secret.data.data },
];

const kube = K8s(kind.Secret, { namespace: ns, name: secretName });

try {
  await kube.Patch(patchOps);
  Log.debug(
    `Successfully updated package secret '${secretName}' in namespace '${ns}'`,
  );
} catch (err) {
  Log.error(
    `Error: Failed to update package secret '${secretName}' in namespace '${ns}': ${JSON.stringify(
      err,
    )}`,
  );
}

[jeff-mccoy]

overall lgtm, small jsdoc issue, but I'lll open a new PR because we have a lot of them

[github-actions]

🎉 This PR is included in version 1.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀