validations_libs.callback_plugins package¶
Submodules¶
- validations_libs.callback_plugins.vf_fail_if_no_hosts module
- validations_libs.callback_plugins.vf_http_json module
- validations_libs.callback_plugins.vf_validation_json module
CallbackModule
CallbackModule.CALLBACK_NAME
CallbackModule.CALLBACK_NEEDS_WHITELIST
CallbackModule.CALLBACK_TYPE
CallbackModule.CALLBACK_VERSION
CallbackModule.v2_playbook_on_handler_task_start()
CallbackModule.v2_playbook_on_no_hosts_matched()
CallbackModule.v2_playbook_on_play_start()
CallbackModule.v2_playbook_on_start()
CallbackModule.v2_playbook_on_stats()
CallbackModule.v2_playbook_on_task_start()
current_time()
secondsToStr()
- validations_libs.callback_plugins.vf_validation_output module
CallbackModule
CallbackModule.CALLBACK_NAME
CallbackModule.CALLBACK_TYPE
CallbackModule.CALLBACK_VERSION
CallbackModule.print_failure_message()
CallbackModule.v2_playbook_on_play_start()
CallbackModule.v2_playbook_on_stats()
CallbackModule.v2_playbook_on_task_start()
CallbackModule.v2_runner_on_failed()
CallbackModule.v2_runner_on_ok()
CallbackModule.v2_runner_on_skipped()
CallbackModule.v2_runner_on_unreachable()
indent()
- validations_libs.callback_plugins.vf_validation_stdout module
Module contents¶
This module contains various callbacks developed to facilitate functions of the Validation Framework.
Somewhat unorthodox naming of the callback classes is a direct result of how ansible handles loading plugins. The ansible determines the purpose of each plugin by looking at its class name. As you can see in the ‘https://github.com/ansible/ansible/blob/devel/lib/ansible/plugins/loader.py’ from the ansible repo, the loader uses the class names to categorize plugins. This means that every callback plugin has to have the same class name, and the unfortunate coder has to discern their purpose by checking their module names.