win_firewall_rule module documents the bypass action which does not exist.

[dieterv]

SUMMARY

• https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/windows/win_firewall_rule.ps1#L172 lists "allow","block","bypass"as possible actions.
• https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/windows/win_firewall_rule.ps1#L38 validates the action parameter and only knows "allow","block"

ISSUE TYPE

• Bug Report

COMPONENT NAME

win_firewall_rule

ANSIBLE VERSION

ansible 2.7.4
  config file = /redacted/ansible.cfg
  configured module search path = ['/home/redacted/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/redacted/ansible/lib/python3.6/site-packages/ansible
  executable location = /home/redacted/ansible/bin/ansible
  python version = 3.6.6 (default, Sep 12 2018, 18:26:19) [GCC 8.0.1 20180414 (experimental) [trunk revision 259383]]

CONFIGURATION

DEFAULT_VAULT_PASSWORD_FILE(/redacted/ansible.cfg) = /redacted/vault_password_file
INVENTORY_ENABLED(/redacted/ansible.cfg) = ['yaml']

OS / ENVIRONMENT

All.

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

[ansibot]

cc @timothyvandenbrande @ar7z1 @dagwieers @jborean93 @jhawkesworth @nitzmahone
click here for bot help

[dagwieers]

Thanks for reporting this! I don't know where the action "bypass" is coming from, according to the (linked) documentation it is not supported by the COM object.

I removed the option from the documentation and arg_spec in #50207, and we are backporting this to the stable-2.7 and stable-2.6 branches. So expect this to be fixed in all upcoming releases.

[dieterv]

Thank you for the quick fix!