You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using azure.azcollection.azure_rm_securitygroup and passing in lists for both destination_port_range and source_address_prefix parameters.
Running the playbook twice should give me ok but is giving me changed.
Edit!
Taking a look at rule vs old_rule in the compare_rules function shows the difference is indeed stringy ports (similar to an issue closed a few years ago):
I incorrectly raised this in the ansible repo (ansible/ansible#74343) and it was closed. Copy/pasting here.
Summary
This might be related to ansible/ansible#26411 which was fixed a few years ago.
I am using
azure.azcollection.azure_rm_securitygroup
and passing in lists for bothdestination_port_range
andsource_address_prefix
parameters.Running the playbook twice should give me
ok
but is giving mechanged
.Edit!
Taking a look at
rule
vsold_rule
in thecompare_rules
function shows the difference is indeed stringy ports (similar to an issue closed a few years ago):old_rule
:rule
:So if I do:
then I get the
ok
I was expecting.Issue Type
Bug Report
Component Name
azure_rm_securitygroup
Ansible Version
Configuration
OS / Environment
Steps to Reproduce
Expected Results
(second run)
Actual Results
(second run)
Code of Conduct
The text was updated successfully, but these errors were encountered: