# Mitigating deprecation of --one-line and associated callback plugin

**URL:** <https://forum.ansible.com/t/mitigating-deprecation-of-one-line-and-associated-callback-plugin/45965>\
**Category:** Guides, FAQs & Howtos\
**Tags:** callback, deprecation, howto\
**Created:** [June 22, 2026, 4:35pm UTC](https://forum.ansible.com/t/mitigating-deprecation-of-one-line-and-associated-callback-plugin/45965 "2026-06-22T16:35:09Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [June 22, 2026, 7:20pm UTC](https://forum.ansible.com/t/mitigating-deprecation-of-one-line-and-associated-callback-plugin/45965/3 "2026-06-22T19:20:37Z")

</div>

I created a thread about keeping that plugin in a collection (instead of everyone having their own fork): [Add oneline callback to a collection (like community.general)?](https://forum.ansible.com/t/45967)

---

_[View the full topic](https://forum.ansible.com/t/mitigating-deprecation-of-one-line-and-associated-callback-plugin/45965)._