End point

You might need multiple End points if you have paths that need to be concluded.

For example, you have a playbook with a script that determines systems have been compromised. One path consists of a function that sends the list to a remote security system that shuts down those systems. There are no need for additional steps so this path concludes in an End point. There's another path that works through a number of scripts, tasks and functions that determines the extent of the problem and alerts all appropriate people and agencies.

For sub-playbooks only, the End point must be configured to store the result value of the sub-playbook or state that there is no result by design. It is in the form of a script where the sub-playbooks result is stored in playbook.results. If no output is needed, use playbook.results = None. For more information, see Playbook operations.