Depend on cdpcli rather than cdpcli-beta

[paulmayer]

Hi,

We are trying to make use of cdpy in some of our automation (indeed also ansible modules) and would ask whether:

• cdpy could be changed to depend on cdpcli rather than cdpcli-beta: installing cdpy in an environment where cdpcli is already present (at least with cdpcli==0.9.117 and cdpy==v1.3.0) causes conflicts in cdpcli/data (aliases.yaml may not include metrics: null, which causes the CLIDriver initialization to fail)
• cdpy could be published to pypi

pre-releases could of course still depend on cdpcli-beta rather than cdpcli, however, stable releases we believe would benefit to rely on cdpcli.

[wmudge]

Hello! Great points! Historically, we had to use the beta of cdpcli in order to get at some endpoints. I am not convinced anymore of this case, so moving to the GA version sounds reasonable.

This question raises a good point about dependencies, though. We have considered dropping the cdpcli dependency and working directly against the CDP Public Cloud endpoints directly, employing local functions to handle the request signing, similar to cdpcurl. (See CDP API Request Signing Specification V1 for details.).

As to publishing to Pypi, that would be ideal and something we have had on the back burner for some time. Stay tuned!