Callback plugin inception

[famedly-bot]

In GitLab by @jcgruenhage on Feb 1, 2023, 09:40

Ansible callback plugins are not all that powerful. Stuff that can't be done right now:

• chaining together pre-processors before handing it over to the callback plugin thats doing the actual logging
• having multiple output streams, where some could be logging to files, some to stdout, etc pp

We'd like to evaluate whether writing a call-back plugin that implements these and then hands off the logging to another call-back plugin would help us for stuff like https://gitlab.com/famedly/infra/meta/-/issues/666

[famedly-bot]

In GitLab by @jcgruenhage on Feb 1, 2023, 09:55

mentioned in issue undefined##undefined

[famedly-bot]

In GitLab by @lrsksr on Feb 10, 2023, 12:16

Talked to David at the CfgMgmtCamp and he said it would probably have a big performance penalty. We need to evaluate this.

[famedly-bot]

In GitLab by @jcgruenhage on Feb 20, 2023, 12:44

Performance is definitely a valid concern here, as we need to check each task return value against each secret, so that might not scale super well, that's true. I don't think it should be that bad though? We need to somehow make sure that we're only checking secrets that apply to the host the task was running against, not every secret, then we should be fine.