# Announcing ansible-lint

**URL:** <https://forum.ansible.com/t/announcing-ansible-lint/13385>\
**Category:** Ansible Project\
**Tags:** ansible-lint\
**Created:** [August 29, 2013, 11:25pm UTC](https://forum.ansible.com/t/announcing-ansible-lint/13385 "2013-08-29T23:25:13Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![Arnon\_Marcus](https://avatars.discourse-cdn.com/v4/letter/a/f475e1/32.png) [@Arnon\_Marcus](https://forum.ansible.com/u/Arnon_Marcus)\
**Post date:** [August 31, 2013, 1:45pm UTC](https://forum.ansible.com/t/announcing-ansible-lint/13385/21 "2013-08-31T13:45:49Z")

</div>

And you can’t escape complexity-growth altogether - you can only strive to minimize it - more advanced use-cases would almost always require more complexity.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [August 31, 2013, 1:46pm UTC](https://forum.ansible.com/t/announcing-ansible-lint/13385/22 "2013-08-31T13:46:43Z")

</div>

I’m not really interested in discussing generalities.

We’ve already said we’re merging these kinds of ideas into core rather than having a seperate tool.

---

<div class="post-metadata">

**Author:** ![Marc\_Tamsky](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@Marc\_Tamsky](https://forum.ansible.com/u/Marc_Tamsky)\
**Post date:** [August 10, 2015, 11:00pm UTC](https://forum.ansible.com/t/announcing-ansible-lint/13385/23 "2015-08-10T23:00:59Z")

</div>

> We’ve already said we’re merging these kinds of ideas into core rather than having a seperate tool.

I took a look around just now, and was unable find any of these ideas, or similar syntax/usage-based warnings in the core.

Two years on, are any of these concepts being included in the v2 roadmap ?

[Previous page](https://forum.ansible.com/t/announcing-ansible-lint/13385.md?page=1)
