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
Ansible module amazon.aws.s3_bucket say "Compatible with AWS, DigitalOcean, Ceph, Walrus, FakeS3 and StorageGRID" but it does not allow specify custom bucket placement rule
amazon.aws.s3_bucket:
ceph: true
name: test03
state: 'present'
region: 'default:default-placement'
....
Couldn't connect to AWS: Provided region_name 'default:default-placement' doesn't match a supported format.
Ceph RGW supports to specify placement constraint using LocationContraint S3's api field
Summary
Ansible module amazon.aws.s3_bucket say "Compatible with AWS, DigitalOcean, Ceph, Walrus, FakeS3 and StorageGRID" but it does not allow specify custom bucket placement rule
Ceph RGW supports to specify placement constraint using LocationContraint S3's api field
https://docs.ceph.com/en/latest/radosgw/placement/#s3-bucket-placement
But amazon botocore does not allow this because of region name validation https://github.com/boto/botocore/blob/7f23afdfdbcab57e319a8d86622b4f0216fc7244/botocore/utils.py#L1315
I thinks it can be difficult to change the ceph caracter separator because it need to update all ceph cluster to take into account
https://github.com/ceph/ceph/blob/08d2bd2b5efdaebc0553f4ca7bdd9d8c66423328/src/rgw/rgw_rest_s3.cc#L2521
Do you think we can ask botocore maintainer to allow disabling region name validation ?
Issue Type
Bug Report
Component Name
amazon.aws.s3_bucket
Ansible Version
Collection Versions
AWS SDK versions
Configuration
$ ansible-config dump --only-changed
OS / Environment
No response
Steps to Reproduce
Expected Results
bucket creation
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: