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
This is just a nice-to-have for symantic sugar, but I would prefer if invoking the backup job would return the newly created history object rather than just a true/false response. This would mean I could immediately pass that response on to my request to mount the snapshot rather than interrogate the history.
It also means if I have overlapping runs of backups (for cloning in different dev/uat environments) that my users are less likely to try and accidently mount the same, last-created, history object rather than the one they just created.
The text was updated successfully, but these errors were encountered:
This is just a nice-to-have for symantic sugar, but I would prefer if invoking the backup job would return the newly created history object rather than just a true/false response. This would mean I could immediately pass that response on to my request to mount the snapshot rather than interrogate the history.
It also means if I have overlapping runs of backups (for cloning in different dev/uat environments) that my users are less likely to try and accidently mount the same, last-created, history object rather than the one they just created.
The text was updated successfully, but these errors were encountered: