Use REST resource mapper

[toddtreece]

Why

This is an attempt to add support for custom resources.

Related issues:

• Add support for deploying custom resources #69
• https://github.com/grafana/cloud-apps-platform/issues/44
• https://github.com/grafana/grafana-multitenancy-team/issues/8

What

• replace static list of resources with DeferredDiscoveryRESTMapper
• update tests

[pablochacin]

Hi @toddtreece Thanks for the PR. The changes look good to me.

[javaducky]

Awesome @toddtreece ! I'm just taking a look at it now.

[javaducky]

Please update examples/ingress_operations.js as this is now broken. Get, List, and Delete operations now require a fully-qualified resource type (Ingress.networking.k8s.io versus Ingress).

Sorry that we have a ton of cruft in the examples directory...many can be ignored as we will be replacing most of them; ingress_operations.js is a newer one that I knew should be working. We'll be getting full integration tests set up in the future.

💪 I was able to install a CRD (K6 type from k6-operator) and perform CRUD operations successfully as well.

[pablochacin]

I was able to install a CRD (K6 type from k6-operator) and perform CRUD operations successfully as well.

yay! It would be nice to add an example of using CRDs 🤔 I'm creating and issue for that.

Sorry that we have a ton of cruft in the examples directory...many can be ignored as we will be replacing most of them;

@javaducky maybe it is time to address this issue. Once we have a clear list of examples we want to maintain, I have some ideas of how to use them to implement #48 based on what I have been doing in xk6-disruptor.

[pablochacin]

@toddtreece I renamed the PR because the title was misleading. Even when the motivation of the PR is to support CRDs the scope is basically introduce the REST mapper. If the scope were to introduce support for CRDs then we should had to add examples and tests for that, what we haven't done in this PR.

[javaducky]

LGTM! Thank you!