redhat.satellite.foreman callback – Sends events to Foreman
Note
This callback plugin is part of the redhat.satellite collection (version 3.10.0).
To install it, use: ansible-galaxy collection install redhat.satellite
.
You need further requirements to be able to use this callback plugin,
see Requirements for details.
To use it in a playbook, specify: redhat.satellite.foreman
.
Callback plugin
This plugin is a notification callback. It sends information for a playbook run to other applications, services, or systems. See Callback plugins for more information on callback plugins.
Synopsis
This callback will report facts and task events to Foreman
Requirements
The below requirements are needed on the local controller node that executes this callback.
whitelisting in configuration
requests (python library)
Parameters
Parameter |
Comments |
---|---|
X509 certificate to authenticate to Foreman if https is used Default: Configuration:
|
|
the corresponding private key Default: Configuration:
|
|
When set, callback does not perform HTTP calls but stores results in a given directory. For each report, new file in the form of SEQ_NO-hostname.json is created. For each facts, new file in the form of SEQ_NO-hostname.json is created. The value must be a valid directory. This is meant for debugging and testing purposes. When set to blank (default) this functionality is turned off. Default: Configuration:
|
|
Toggle to make the callback plugin disable itself even if it is loaded. It can be set to ‘1’ to prevent the plugin from being used even if it gets loaded. Default: Configuration:
|
|
URL of the Foreman Smart Proxy server. Configuration:
|
|
endpoint type for reports: foreman or proxy Default: Configuration:
|
|
URL of the Foreman server. Configuration:
|
|
Toggle to decide whether to verify the Foreman certificate. It can be set to ‘1’ to verify SSL certificates using the installed CAs or to a path pointing to a CA bundle. Set to ‘0’ to disable certificate checking. Default: Configuration:
|
Hint
Configuration entries for each entry type have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up.