I raised https://github.com/Commvault/cvpysdk/issues/191 for the immediate need we have, but in general I would like to raise more awareness to ensure Commvault SDK’s do not keep on using deprecated API calls going forward.
Could someone please own the SDK updates in case a specific API call is deprecated to ensure the correct API endpoints are being used?
Thanks!
Best answer by MaheshPrakash
@mikevg we have corrected the way we notify about new versions, we will not remove the existing API, we want customers to urge using newer versions for better alignment with UI and standards. For example now on the same link we say that there is a newer version available to use instead of mentioning it as deprecated.
@mikevg we have corrected the way we notify about new versions, we will not remove the existing API, we want customers to urge using newer versions for better alignment with UI and standards. For example now on the same link we say that there is a newer version available to use instead of mentioning it as deprecated.
The last part about SDK’s showing your intent (consume the newer API’s) is still open tho. Any chance we can see Commvault leading the way by ensuring the SDK’s use the latest API’s too?
Yes @mikevg we can take that up internally to change it, it is a considerable effort which can also be regressive, since we are not going to deprecate the older versions of endpoints, we do not want to focus our time on changing the version at the moment. But we will move them in the future once we find some cycles.
I should have added why this needs to be done… Our developers look at the API and see the SDK’s and look there for how it was implemented. I cannot count the amount of times our customers developers went crazy with undocumented API’s used in the SDK’s and the documented ones not being used.
I understand it might be a lot of work, but then again if you do not lead by example the overall experience by people who want to use the API shy away if vendors do not even use the API’s that are documented and opt to use an undocumented one.
Please include this in your decisions/strategy/roadmap