Allow hash suffixing of arbitrary types

[tinselspoon]

When using a custom generator plugin, the kustomize.config.k8s.io/needs-hash hash suffix generator only works for ConfigMap and Secret resources, and fails the build process if used on a different type of resource. I had hit the exact same issue as described in #1167, where I wanted to use a generator plugin to create a custom SealedSecret resource with a hash suffix, as it should behave the same as a built-in Secret.

This change applies the suggested approach commented in #1167 (before it was auto-closed for inactivity) which is to hash the entire object for unknown types.

I appreciate the original issue is a little old and this approach may no longer be wanted, but I wanted to put this for your consideration just in case.

[k8s-ci-robot]

Welcome @tinselspoon!

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 @tinselspoon. 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/test-infra repository.

[monopole]

Sure, sounds good.
FYI, we're removing all apimachinery dependence (#2506) as it unblocks a great number of things.
This doesn't look like it makes that problem harder.
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: monopole, tinselspoon

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [monopole]

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

[tinselspoon]

Thank you!