-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
e2c_vpc_nacl_info fails if no NACL are found #2425
Comments
branic
added a commit
to branic/amazon.aws
that referenced
this issue
Dec 20, 2024
branic
added a commit
to branic/amazon.aws
that referenced
this issue
Dec 20, 2024
alinabuzachis
pushed a commit
to alinabuzachis/amazon.aws
that referenced
this issue
Jan 15, 2025
…lections#2425) (ansible-collections#2429) SUMMARY Only fail listing NetworkACLs if specific ACLs were requested and not found. Fixes: ansible-collections#2425 ISSUE TYPE Bugfix Pull Request COMPONENT NAME ec2_vpc_nacl_info ADDITIONAL INFORMATION Reviewed-by: Mark Chappell
alinabuzachis
pushed a commit
to alinabuzachis/amazon.aws
that referenced
this issue
Jan 15, 2025
…lections#2425) (ansible-collections#2429) SUMMARY Only fail listing NetworkACLs if specific ACLs were requested and not found. Fixes: ansible-collections#2425 ISSUE TYPE Bugfix Pull Request COMPONENT NAME ec2_vpc_nacl_info ADDITIONAL INFORMATION Reviewed-by: Mark Chappell
mandar242
pushed a commit
to mandar242/amazon.aws
that referenced
this issue
Feb 3, 2025
…lections#2425) (ansible-collections#2429) SUMMARY Only fail listing NetworkACLs if specific ACLs were requested and not found. Fixes: ansible-collections#2425 ISSUE TYPE Bugfix Pull Request COMPONENT NAME ec2_vpc_nacl_info ADDITIONAL INFORMATION Reviewed-by: Mark Chappell (cherry picked from commit 7b5212d)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: