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
If you specify --all, or provide a snapset, then the code performs operations on several volumes. For example, if a snapset of 5 volumes are passed in, and the operations are successful on the first 4, then the 5th one fails, the user has no way to know which of those operations were successful. The response should contain information about each volume e.g.
result:
return_code: N # if there are any errors, this will be the return_code of the last errorchanged: true|false # if there are any changes, this will be trueresults:
- name: name argument for snapset element, if givenvg: volume group, if givenlv: logical volume, if givenreturn_code: N # code from operationchanged: true|false # if the operation changed somethingmessage: .... # message from the operation
- name: ........
If you specify
--all
, or provide a snapset, then the code performs operations on several volumes. For example, if a snapset of 5 volumes are passed in, and the operations are successful on the first 4, then the 5th one fails, the user has no way to know which of those operations were successful. The response should contain information about each volume e.g.We could also have a config parameter -
snapshot_fail_fast: true|false
- if true, once it hits the first failure, it returns without processing all of the items in the snapset. If false, it will process all of them.This is similar to how Ansible returns results from a loop - https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_loops.html#registering-variables-with-a-loop
The text was updated successfully, but these errors were encountered: