# Playbook-wide Jinja2 macros

**URL:** <https://forum.ansible.com/t/playbook-wide-jinja2-macros/922>\
**Category:** Get Help\
**Tags:** playbook, jinja2\
**Created:** [September 19, 2023, 11:40am UTC](https://forum.ansible.com/t/playbook-wide-jinja2-macros/922 "2023-09-19T11:40:39Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\
**Post date:** [October 12, 2023, 9:20am UTC](https://forum.ansible.com/t/playbook-wide-jinja2-macros/922/8 "2023-10-12T09:20:02Z")

</div>

> [@nitzmahone](#):
>
> Anyway, probably worth some discussion, but just want to make sure everyone’s considering the blast radius to Ansible’s entire ecosystem…

> [@utoddl](#):
>
> If macro plugins were available – and restricted to collections would be fine

I’d be **delighted** to see that discussed over in #Project Discussions, for the record. Discoverable reasoning, linkable explanations (thank **you** @nitzmahone!) and ecosystem-wide involvement is _exactly_ why I want this forum to take off 😛

Meanwhile I’m marking Nitz’s answer as the solution, because the question was “is it possible” and the answer is “yes it’s possible” 😃

---

_[View the full topic](https://forum.ansible.com/t/playbook-wide-jinja2-macros/922)._