Using V1Alpha Over V1

[TimDiam0nd]

Hi

After spending an embarrassingly long time, i noticed that many of the funcs were updated in 7761868 to use the v1 base url over the v1alpha base url.

The issue i have is that i would like to use the v1alpha url instead, because i want to get the datatables associated with a rule when calling chronicle.list_rules().

Would you be open a to a pr allowing the base url to be configurable (i.e. by default use v1 when exists, but otherwise use v1alpha) when initialising the chronicle client?

Thanks

[mihirvala08]

Hi @TimDiam0nd,
Changes in method using v1 endpoints are method level changes rather then at client initialization.
So, for now we only need to have flag/configuration to use v1alpha instead in method level only.

Once, all/most of the methods migrates to v1 then we can have configuration flag at client initialization to use v1 or v1alpha.

As Long as we don't change current methods default behavior, this should be fine.

[TimDiam0nd]

Agreed, method level is also important.

Later on today ill make a start on this.

[danieleforberghi]

Also recognized that the underlying api is using v1alpha, so it cannot be changed at this stage?

[mihirvala08]

Also recognized that the underlying api is using v1alpha, so it cannot be changed at this stage?

Rules, Rule deployment, retro hunt and reference list endpoints have been updated to V1 from v1alpha.
Other endpoints are still on v1Alpha and will get updated to v1 whenever it gets available publicly.

For endpoint migrated to v1, there can be flag provided to switch between v1 and v1alpha endpoint.

[mihirvala08]

Closing as #150 is merged and released.