# Content: New Parameter in Multiple something\_config Ansible Modules

DevFeed: [Content: New Parameter in Multiple something\_config Ansible Modules](<https://devfeed.tech/articles/content-new-parameter-in-multiple-something-config-ansible-modules-11413.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/07/ansible-config-content/>)

Published: 2026-07-15T05:22:00Z

Content type: opinion

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Ansible](<https://devfeed.tech/topics/ansible.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Network](<https://devfeed.tech/topics/network.md>), [issue tracker](<https://devfeed.tech/topics/issue-tracker.md>)

Tags: [ansible](<https://devfeed.tech/tags/ansible.md>), [network](<https://devfeed.tech/tags/network.md>)

## AI overview

The article discusses new parameters added to several Ansible network device configuration modules after concerns about templating behavior and a change introduced in Ansible 12. It describes the author's issue report and notes that the issue's closure was due to poor issue management rather than rejection of the proposed solution.

## Source excerpt

Last December, I wrote a pretty ranty post explaining how Ansible release 12 broke (some?) network device configuration playbooks. The inevitable anonymous troll (why are they always anonymous?) couldn't resist asking whether I opened an issue on GitHub. I didn't (more about that later), but when the solution to that rant was "we're deprecating using templates in src" parameter, I opened an issue arguing why that's not a good idea. Read more ...