You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I can see that there is some acknowledgement about SDK compatibility in the README, but it's not expansive enough.
Can we get a table of which SDK version should be used with which Rubrik Security Cloud version?
What would be even more helpful is to be able to get this information in some sort of automated fashion. My company utilizes this PowerShell module as a dependency for other modules, and it is difficult to know when we need to bump our dependency version. We have an automated process for updating module dependencies to proper versions, and we could implement a query to decide what to do. Perhaps even an integrated function that spits out compatibility info?
As of right now, we simply have to wait for it to break, then hope that a bump of the SDK to the latest version solves the problem. Since we don't have control over when Rubrik updates its cloud, this leaves us in a vulnerable and confused sort of state.
The text was updated successfully, but these errors were encountered:
Currently, I can see that there is some acknowledgement about SDK compatibility in the README, but it's not expansive enough.
Can we get a table of which SDK version should be used with which Rubrik Security Cloud version?
What would be even more helpful is to be able to get this information in some sort of automated fashion. My company utilizes this PowerShell module as a dependency for other modules, and it is difficult to know when we need to bump our dependency version. We have an automated process for updating module dependencies to proper versions, and we could implement a query to decide what to do. Perhaps even an integrated function that spits out compatibility info?
As of right now, we simply have to wait for it to break, then hope that a bump of the SDK to the latest version solves the problem. Since we don't have control over when Rubrik updates its cloud, this leaves us in a vulnerable and confused sort of state.
The text was updated successfully, but these errors were encountered: