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
When I try to get a list of VPC NACLs an Unable to describe ACL. NetworkAcl does not exist error is returned from the module.
This error was not observed when this module was part of the community.aws collection. In the community.aws version of the module if there were no NACLs found an empty list would be returned.
Causing the module to fail when there are no NACLs found is not helpful (IMHO). For example, I need to get the NACLs that match a filter (in my case that they are the non-default NACLs) and do further processing with the ones that are returned from the query. If there are no NACLs that match the query that is fine (the further processing becomes a NOP), but having the module fail just because the query returns no results causes the entire play to fail.
I expected that the module would return an empty list of nacls
For comparison, when running the playbook with the community.aws version 8.0.0 installed the result that is registered in the region_nacls variable in the above playbook is:
Summary
When I try to get a list of VPC NACLs an
Unable to describe ACL. NetworkAcl does not exist
error is returned from the module.This error was not observed when this module was part of the
community.aws
collection. In thecommunity.aws
version of the module if there were no NACLs found an empty list would be returned.Causing the module to fail when there are no NACLs found is not helpful (IMHO). For example, I need to get the NACLs that match a filter (in my case that they are the non-default NACLs) and do further processing with the ones that are returned from the query. If there are no NACLs that match the query that is fine (the further processing becomes a NOP), but having the module fail just because the query returns no results causes the entire play to fail.
Issue Type
Bug Report
Component Name
ec2_vpc_nacl_info
Ansible Version
Collection Versions
AWS SDK versions
Configuration
OS / Environment
RHEL 9.5
Steps to Reproduce
This playbook succeeds when
community.aws
version 8.0.0 is installed, but fails whenamazon.aws
version 9.1.0 is installed.Expected Results
I expected that the module would return an empty list of
nacls
For comparison, when running the playbook with the
community.aws
version 8.0.0 installed the result that is registered in theregion_nacls
variable in the above playbook is:Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: