Endpoint conflict between instance, registry and baremetal

[korridor]

Endpoints like ListServers or ListImages are in multiple namespaces and there functions are overwriting each other.

[FGRibreau]

Happy to accept a PR for it! 👍

[mcoolive]

Hi,

I can work on a PR. But I have a question on the design. Should we simply rename some functions ? Or should we rework the actual SCW-Client and cut it into several APIs ? The first option is simpler to implement. The second option is a big breaking change.

More detail about how I think to divide the actual client:

• a smaller client that just hold the common axis config (see ticket Use axios global config #1)
• API objects that wrap the client and provide functions limited to: instances, baremetal, etc.
• this would presents a naming similar to what is achieved by Scaleway-sdk-go

[FGRibreau]

Hello @mcoolive :)
I would go with option two, we will release another major version but it will be way simpler for users, I should have made it that way on the first iteration, sorry ^^'

[mcoolive]

So, should I wait? Or are you interesting by a PR ?

[FGRibreau]

Interested by a PR yes for reworking the client into multiple sub-clients (one for each functions (instances, baremetal, ...)).