feat: add optional strict unmarshalling for LoadFunctionConfig and SimpleProcessor

[lorenzofelletti]

Motivation

When using SimpleProcessor one may want to have strict unmarshalling for the function config and throw an error if any unknown field is supplied in the configuration.

The current behaviour does not allow this flexibility. Adding strict option to LoadFunctionConfig and adding a Strict field to SimpleProcessor allows to programmatically change the unmarshalling behaviour, while keeping the current behaviour as the default.

Changes

• Introduced a new boolean field Strict in the SimpleProcessor struct to control strict unmarshalling behavior when loading function configurations.
• Updated the LoadFunctionConfig function to accept the strict parameter, allowing it to use strict unmarshalling.
• Modified SimpleProcessor to be able to control the behaviour
• Modified VersionedAPIProcessor, and TemplateProcessor to pass strict false.
• Added unit tests for LoadFunctionConfig to cover scenarios for strict mode, including successful loads and failure cases for unknown fields.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: lorenzofelletti / name: Lorenzo Felletti (e963d62, fcf54f5)

[k8s-ci-robot]

Welcome @lorenzofelletti!

It looks like this is your first PR to kubernetes-sigs/kustomize 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kustomize has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @lorenzofelletti. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lorenzofelletti
Once this PR has been reviewed and has the lgtm label, please assign koba1t for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

This PR has multiple commits, and the default merge method is: merge.
You can request commits to be squashed using the label: tide/merge-method-squash

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.