<h5 dir="auto">ISSUE TYPE</h5>
<ul dir="auto">
<li>Feature Idea</li>
</ul>
<h5 dir="auto">COMPONENT NAME</h5>
<p dir="auto">group<br>
user<br>
ALL (almost)</p>
<h5 dir="auto">ANSIBLE VERSION</h5>
<p dir="auto">N/A</p>
<h5 dir="auto">CONFIGURATION</h5>
<p dir="auto">N/A</p>
<h5 dir="auto">OS / ENVIRONMENT</h5>
<p dir="auto">N/A</p>
<h5 dir="auto">SUMMARY</h5>
<p dir="auto">All users need all the time to support optional parameteres when using modules. Eg for group module for gid the "" or 0 etc. are not suitable values:</p>
<ul dir="auto">
<li>
<p dir="auto">group:<br>
gid: '{{ user.gid | default("") }}'<br>
...</p>
</li>
<li>
<p dir="auto">user:<br>
uid: '{{ user.uid | default("") }}'<br>
...</p>
</li>
</ul>
<p dir="auto">So for group, user etc. modules there is needed to be duplicate code to support if parameter is defined or not (and module's default value should be used). Now the duplicated code would eg. use when clause to have the wanted functionality. It's bad.</p>
<p dir="auto">Could Ansible have default value to support this?</p>
<h5 dir="auto">Issue Type:</h5>
<p dir="auto">Bug Report</p>
<h5 dir="auto">Ansible Version:</h5>
<p dir="auto">ansible 1.6</p>
<h5 dir="auto">Environment:</h5>
<p dir="auto">Mac OS X 10.7</p>
<h5 dir="auto">Summary:</h5>
<p dir="auto">rules_egress was added to ec2_group in 1.6 (previous there was no rules_egress).  Unfortunately it defaults to nothing in it, meaning that previous ansible scripts will not allow anything out of a security group.  This breaks many security groups.</p>
<h5 dir="auto">Steps To Reproduce:</h5>
<p dir="auto">Create a ec2_group (security group) with no rules_egress.  Watch everything get blocked going outbound.</p>
<h5 dir="auto">Expected Results:</h5>
<p dir="auto">Should default to allowing everything outbound since thats what ansible did previously.</p>
<h5 dir="auto">Actual Results:</h5>
<p dir="auto">Unable to access going outbound.</p>