# adding insecure option to nova\_compute

**URL:** <https://forum.ansible.com/t/adding-insecure-option-to-nova-compute/17171>\
**Category:** Ansible Project\
**Created:** [January 2, 2015, 8:16pm UTC](https://forum.ansible.com/t/adding-insecure-option-to-nova-compute/17171 "2015-01-02T20:16:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Drew\_Tranquada](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@Drew\_Tranquada](https://forum.ansible.com/u/Drew_Tranquada)\
**Post date:** [January 2, 2015, 8:16pm UTC](https://forum.ansible.com/t/adding-insecure-option-to-nova-compute/17171/1 "2015-01-02T20:16:02Z")

</div>

Hello all,  
I was reading the directions on submitting bug reports/features and it was mentioned that we ask before we submit a PR to see if it is worth it.  
We currently have our ssl certs setup in all sorts of nasty and incorrectness, and its not very feasible to change at this point. Because of this,  
we have to specify insecure=True when using nova client or it complains about ssl being incorrect (which we know it is) and will not progress any further.  
I noticed that the nova\_compute ansible core plugin does not have an option to specify insecure, so it will never work for us.  
I have a 2 line patch that adds the functionality to the core module (leaving insecure=False by default of course), then in your playbook you would just  
specify insecure: True .  
[http://pastebin.com/AZN4XKWN](http://pastebin.com/AZN4XKWN)

Is this something that could be added to the core module since it is supported by nova client or would this be shot down so I shouldn’t bother attempting a PR?

Thank you.