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
I would expect the facts plan to always add facts to the inventory for successful nodes, even if it failed on some nodes.
Describe the Solution You Would Like
The facts task should catch errors and then call add_facts for successful nodes. Then either fail the plan with the original error, or return $result_set if all succeeded. However, I could be missing an important reason for why add_facts and the facts task are independent of each other in the first place.
Describe Alternatives You've Considered
I'm currently using a wrapper plan which does the above. This lets me run facts for a bunch of nodes and at least continue on even if we failed to collect facts for some nodes.
The text was updated successfully, but these errors were encountered:
Use Case
I would expect the
facts
plan to always add facts to the inventory for successful nodes, even if it failed on some nodes.Describe the Solution You Would Like
The
facts
task should catch errors and then calladd_facts
for successful nodes. Then either fail the plan with the original error, or return$result_set
if all succeeded. However, I could be missing an important reason for whyadd_facts
and thefacts
task are independent of each other in the first place.Describe Alternatives You've Considered
I'm currently using a wrapper plan which does the above. This lets me run facts for a bunch of nodes and at least continue on even if we failed to collect facts for some nodes.
The text was updated successfully, but these errors were encountered: