<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/content-new-parameter-in-multiple-something-phkoomstn" -->

---
title: Content: New Parameter in Multiple something | daily.dev
description: Ansible's cisco.ios.ios_config and arista.eos.eos_config modules have gained a new `content` parameter that accepts rendered configuration as a string. This...
canonical: https://daily.dev/posts/content-new-parameter-in-multiple-something-phkoomstn
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Content: New Parameter in Multiple something | daily.dev
og:description: Ansible's cisco.ios.ios_config and arista.eos.eos_config modules have gained a new `content` parameter that accepts rendered configuration as a string. This...
og:url: https://daily.dev/posts/content-new-parameter-in-multiple-something-phkoomstn
og:image: https://api.daily.dev/og/posts/phkOoMsTN.png
og:image:alt: Content: New Parameter in Multiple something
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Content: New Parameter in Multiple something

**[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 1 min read · 0 upvotes · 0 comments

## Summary

Ansible's cisco.ios.ios_config and arista.eos.eos_config modules have gained a new `content` parameter that accepts rendered configuration as a string. This resolves a long-standing issue where Ansible 12 broke network device configuration playbooks that relied on templating in the `src` parameter. The `src` parameter's templating capability is slated for deprecation, and the new `content` parameter is the recommended replacement. The change appears to have been applied across multiple device configuration modules.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.ipspace.net/2026/07/ansible-config-content>

## Questions this post answers

### What is the new `content` parameter in Ansible ios_config and eos_config modules and why was it added?

The `content` parameter accepts a pre-rendered configuration string directly, replacing the need to use Jinja2 templating inside the `src` parameter. It was added after Ansible 12 broke network device configuration playbooks that relied on `src` templating. The `src` parameter's templating capability is being deprecated, and `content` is the recommended migration path for cisco.ios.ios_config, arista.eos.eos_config, and likely other device config modules.

_Network engineers migrating Ansible playbooks away from src templating track changes like this on daily.dev._

## Similar posts on daily.dev

- [Deep Dive: Automating NetOps with the cisco.catalystcenter Ansible Collection](https://daily.dev/posts/deep-dive-automating-netops-with-the-cisco-catalystcenter-ansible-collection-2bstaaosj) · Cisco · 0 upvotes · 0 comments
- [What’s new in Ansible Certified Content Collection for AWS](https://daily.dev/posts/what-s-new-in-ansible-certified-content-collection-for-aws-tugkon68u) · Red Hat Developer · 0 upvotes · 0 comments
- [Ansible Fetch Module: How it Works & Examples](https://daily.dev/posts/ansible-fetch-module-how-it-works-examples-csmuasw4u) · Spacelift · 2 upvotes · 0 comments
- [The Crappy Cisco IOS CLI Error Reporting « ipSpace.net blog](https://daily.dev/posts/the-crappy-cisco-ios-cli-error-reporting-ipspace-net-blog-2cshblas0) · ipSpace.net Blog · 0 upvotes · 0 comments

---

Tags: [#networking](https://daily.dev/tags/networking), [#ansible](https://daily.dev/tags/ansible)

[View this post on daily.dev](https://daily.dev/posts/content-new-parameter-in-multiple-something-phkoomstn)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Content: New Parameter in Multiple something","url":"https://daily.dev/posts/content-new-parameter-in-multiple-something-phkoomstn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/content-new-parameter-in-multiple-something-phkoomstn"},"datePublished":"2026-08-11T08:54:11.723Z","dateModified":"2026-08-24T07:03:16.998Z","description":"Ansible's cisco.ios.ios_config and arista.eos.eos_config modules have gained a new `content` parameter that accepts rendered configuration as a string. This...","image":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","thumbnailUrl":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","isAccessibleForFree":true,"articleSection":"ipSpace.net Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ipSpace.net Blog","logo":"https://media.daily.dev/image/upload/s--xS7E82MT--/f_auto,q_auto/v1786438303/logos/ipspace?_a=BAMAMicg0","url":"https://daily.dev/sources/ipspace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/content-new-parameter-in-multiple-something-phkoomstn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"networking,ansible","timeRequired":"PT1M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ipSpace.net Blog","item":"https://daily.dev/sources/ipspace"},{"@type":"ListItem","position":3,"name":"Content: New Parameter in Multiple something"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/content-new-parameter-in-multiple-something-phkoomstn#faq","mainEntity":[{"@type":"Question","name":"What is the new `content` parameter in Ansible ios_config and eos_config modules and why was it added?","acceptedAnswer":{"@type":"Answer","text":"The `content` parameter accepts a pre-rendered configuration string directly, replacing the need to use Jinja2 templating inside the `src` parameter. It was added after Ansible 12 broke network device configuration playbooks that relied on `src` templating. The `src` parameter's templating capability is being deprecated, and `content` is the recommended migration path for cisco.ios.ios_config, arista.eos.eos_config, and likely other device config modules. Network engineers migrating Ansible playbooks away from src templating track changes like this on daily.dev."}}]}
```

