# adding an the ability to do --security to the yum core module

**URL:** <https://forum.ansible.com/t/adding-an-the-ability-to-do-security-to-the-yum-core-module/24334>\
**Category:** Ansible Developer\
**Created:** [April 27, 2017, 1:21am UTC](https://forum.ansible.com/t/adding-an-the-ability-to-do-security-to-the-yum-core-module/24334 "2017-04-27T01:21:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jerry1](https://avatars.discourse-cdn.com/v4/letter/j/8c91f0/32.png) [@jerry1](https://forum.ansible.com/u/jerry1)\
**Post date:** [April 27, 2017, 1:21am UTC](https://forum.ansible.com/t/adding-an-the-ability-to-do-security-to-the-yum-core-module/24334/1 "2017-04-27T01:21:23Z")

</div>

Hi,

I have been doing a bunch of ansible stuff for my company recently. A team member came to me and said she really wants to be able to a “yum update --security” from ansible. Using a command: is always possible but gross given there is a yum core module and we can’t be the only people who want to do this.

I took a look at it and it doesn’t seem like it would be to hard to add this and am happy to do the work. The code is more terse than I like, but I can match the coding style. My thought on implementing this is to add another parameter to yum called options and it takes a single string or an array of strings. The parser would pass that down to ensure, who would test to see if it was a singleton or an array and then append it to command line early in the command line constructing process.

If people are uncomfortable with handing the users a running chainsaw, I could do something more targeted like security\_only as a boolean. I am really open to doing this any way that the community thinks is best.

If I do this and the code is reasonable, would it be likely to have this pulled back into the mainline?

thanks in advance  
jerry