ansible/ansible-modules-core — pull request #317 by maxamillion (2014-11-13 21:34:44+00:00)
Title: fix gce_net add firewall rule example

This is a tiny patch, it's only documentation. At the time of this writing, the [gce_net module example](http://docs.ansible.com/gce_net_module.html) for adding a firewall rule doesn't actually add the firewall rule becuase it's misssing the fwname field to name the firewall rule.

Here's a simple task I tested with:
```yaml
- name: Create firewall rule
gce_net:
service_account_email: "{{ gce_service_account_email }}"
pem_file: "{{ gce_pem_file }}"
project_id: "{{ gce_project_id }}"
name: "{{ oo_network }}"
fwname: all-ssh
allowed: tcp:22
src_tags: ['ssh']
register: gce_net

```

This is what happens if you run without a firewall rule name:
```
TASK: [Create firewall rule] **************************************************
ok: [localhost] => {"changed": false, "ipv4_range": "10.240.16.0/24", "name": "amtestnet", "state": "present"}
```

And with the fwname provided:
```
TASK: [Create firewall rule] **************************************************
changed: [localhost] => {"allowed": "tcp:22", "changed": true, "fwname": "all-ssh", "ipv4_range": "10.240.16.0/24", "name": "amtestnet", "src_range": null, "src_tags": ["ssh"], "state": "present"}
```

(Also, random note ... it looks like one of my vim plugins cleaned up some whitespace also. If that's a problem I can resubmit without those changes.)