Setup mocks

[cyx]

Description

In order to provide easier testability, we're going to utilize https://github.com/golang/mock. For us to utilize that, we'll want to have clear interfaces we can mock.

Unfortunately, the go sdk today doesn't have that, so we're going to shim interfaces / functions which would allow us to mock cleanly.

Changes

• Uses golang/mock/mockgen to generate mock files.
• Uses golang/mock/go-mock to work with mocks during the client test.
• Adds a client test for listing to show it working for one spot.
• Adds an internal/auth0 package to create a point of mocking.
• Adds internal/auth0.API struct to hold our interface style management client.

[cyx]

This is important so we can vendor our tooling deps.

[vprasanth]

Why not pass the token details instead and make the client directly here?

[cyx]

It's basically because the management constructor having a plethora of options and encoding that vs catching a fully formed struct being easier

[paddycarey]

I like it 👍🏻

I wonder though if we should specify more minimal interfaces, only the methods we're actually using to keep the verbosity down. On the other hand, if the goal is to just get something working such that we can later push the interfaces (and maybe even the mocks) upstream then great, that works too.

[cyx]

I like it 👍🏻

I wonder though if we should specify more minimal interfaces, only the methods we're actually using to keep the verbosity down. On the other hand, if the goal is to just get something working such that we can later push the interfaces (and maybe even the mocks) upstream then great, that works too.

Yes the intention is for us to upstream this, or basically push the envelope in terms of the current sdk's limitations