# parsing YAML vs sudo

**URL:** <https://forum.ansible.com/t/parsing-yaml-vs-sudo/13124>\
**Category:** Ansible Project\
**Created:** [July 15, 2013, 3:12pm UTC](https://forum.ansible.com/t/parsing-yaml-vs-sudo/13124 "2013-07-15T15:12:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Lucas](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@Michael\_Lucas](https://forum.ansible.com/u/Michael_Lucas)\
**Post date:** [July 15, 2013, 3:12pm UTC](https://forum.ansible.com/t/parsing-yaml-vs-sudo/13124/1 "2013-07-15T15:12:03Z")

</div>

Hi,

It would be really nice if ansible would parse the playbook YAML  
before requesting the sudo password.

I'm just learning YAML, and rely on ansible to tell me I'm wrong. I'm  
frequently wrong.

Our company's ansible account has a tedious and annoying sudo  
password. (It's not security through obscurity, it's security through  
"I can't even type the damn thing.")

> From a user perspective, this seems like an easy change to make. Any

chance your could add this to ansible, even as an option in  
ansible.cfg or something?

Thanks,  
==ml

---

<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:** [July 15, 2013, 3:14pm UTC](https://forum.ansible.com/t/parsing-yaml-vs-sudo/13124/2 "2013-07-15T15:14:51Z")

</div>

Thanks for providing the extended explanation vs the twitter (much better!)

Sure, this sounds reasonable.

Please make sure there’s a github ticket so we can have a record of this!

[github.com/ansible/ansible](http://github.com/ansible/ansible)

Thanks!

---

<div class="post-metadata">

**Author:** ![Michael\_Lucas](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@Michael\_Lucas](https://forum.ansible.com/u/Michael_Lucas)\
**Post date:** [July 15, 2013, 3:39pm UTC](https://forum.ansible.com/t/parsing-yaml-vs-sudo/13124/3 "2013-07-15T15:39:35Z")

</div>

Issue 3535.

Wasn't sure if it was worth an issue, or even a mailing list query,  
but hey, I'm not gonna argue.

==ml