-
Notifications
You must be signed in to change notification settings - Fork 342
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
unsure if module_defaults is supported anymore for ec2 modules #557
Comments
Files identified in the description:
If these files are inaccurate, please update the |
@IPvSean what happens if you use |
This is the module->
|
Could you try dropping the "amazon.aws"? |
OK that works.... so if I use amazon.aws on any of the modules trying to use the defaults it will break, if I use the short name, it will work so this works->
|
It looks like a duplicate of the issue ansible/ansible#76171 is fixing. It's fixed in ansible-core 2.12 because we resolve and cache the action groups rather than just taking them as-is. The |
Add missing entry to AWS action group SUMMARY When migrating ec2_instance we missed adding the ec2_instance_facts alias to the AWS action group ISSUE TYPE Bugfix Pull Request COMPONENT NAME meta/runtime.yml ADDITIONAL INFORMATION fixes: #557 Reviewed-by: Alina Buzachis <None> Reviewed-by: None <None>
Hi @IPvSean, The missing entry has now been added to module_defaults. We hope to have the next release (2.1.0) of amazon.aws out in the next couple of weeks. As @s-hertel outlined, there's also the open issue with Ansible itself that means you currently need to use the "short" name rather than it's fully-qualified name. Because that's a backport it's not automatically merged but it looks like it's got the necessary approvals so hopefully that will be available in a released version of 2.11 'soon' (already fixed in 2.12). |
Add missing entries to AWS action group SUMMARY A couple of entries are missing from the AWS action group ISSUE TYPE Bugfix Pull Request COMPONENT NAME meta/runtime.yml ADDITIONAL INFORMATION Spotted while investigating ansible-collections/amazon.aws#557 Reviewed-by: Alina Buzachis <None> Reviewed-by: None <None>
Prepare 1.5.0 release Reviewed-by: https://github.com/apps/ansible-zuul
Summary
I have the following in my play header->
Here is an example task->
I am getting this error->
Issue Type
Bug Report
Component Name
ec2_instance_facts
Ansible Version
$ ansible --version
Collection Versions
$ ansible-galaxy collection list
AWS SDK versions
$ pip show boto boto3 botocore
Configuration
$ ansible-config dump --only-changed
OS / Environment
RHEL 8
Steps to Reproduce
Expected Results
No error with missing region
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: