-
Notifications
You must be signed in to change notification settings - Fork 397
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
S3 community.aws.aws_s3_cors rules error #404
Labels
Comments
Files identified in the description: If these files are inaccurate, please update the |
The issue was introduced with community.aws version 1.1.0. |
jillr
pushed a commit
that referenced
this issue
Feb 11, 2021
* #404 fix wrong element spec for rules param * #404 documentation fix Co-authored-by: Markus Bergholz <[email protected]>
ethemcemozkan
pushed a commit
to ethemcemozkan/community.aws
that referenced
this issue
Feb 18, 2021
…tions#408) * ansible-collections#404 fix wrong element spec for rules param * ansible-collections#404 documentation fix Co-authored-by: Markus Bergholz <[email protected]>
alinabuzachis
pushed a commit
to alinabuzachis/community.aws
that referenced
this issue
Jul 19, 2021
…tions#408) * ansible-collections#404 fix wrong element spec for rules param * ansible-collections#404 documentation fix Co-authored-by: Markus Bergholz <[email protected]>
alinabuzachis
pushed a commit
to alinabuzachis/community.aws
that referenced
this issue
Jul 19, 2021
…tions#408) * ansible-collections#404 fix wrong element spec for rules param * ansible-collections#404 documentation fix Co-authored-by: Markus Bergholz <[email protected]>
danielcotton
pushed a commit
to danielcotton/community.aws
that referenced
this issue
Nov 23, 2021
…tions#408) * ansible-collections#404 fix wrong element spec for rules param * ansible-collections#404 documentation fix Co-authored-by: Markus Bergholz <[email protected]>
alinabuzachis
pushed a commit
to alinabuzachis/community.aws
that referenced
this issue
May 25, 2022
…nsible-collections#404) Add constraints.txt and requirements.txt for unit/integration tests SUMMARY Now that we state that we support specific minimum versions of the AWS SDKs, make sure we base our unit/integration tests against them such that modules need to explicitly test/request newer versions of the SDKs. ISSUE TYPE Feature Pull Request COMPONENT NAME tests/integration tests/unit ADDITIONAL INFORMATION Once merged into amazon.aws we should merge this into community.aws Depends-On: ansible-collections#453 Depends-On: ansible-collections#454 Depends-On: ansible-collections#450 Depends-On: ansible-collections#496 See also: ansible/ansible-zuul-jobs#991 Reviewed-by: Jill R <None> Reviewed-by: None <None>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
Switching to Ansible 2.10 from 2.9 using the collection module community.aws.aws_s3_cors rules I receive the following error trying to add cors rules to an s3 bucket. Previously using the same input arguments it succeeded without issues.
Input Args:
Error:
The problem can be solved by changing rules arg spec to
rules=dict(type='list'),
ISSUE TYPE
COMPONENT NAME
community.aws.aws_s3_cors rules
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Ubuntu Focal
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: