Re: [Pulp-list] Issues with using S3 storage when running pulp on Amazon EC2 (pulp3)

2019-11-09 Thread David Davis
You should be able to set aws_default_acl to null (ie "aws_default_acl: ~" or "aws_default_acl: null"). Sounds like that's not working though. What error did you get? Would you mind filing an issue? https://pulp.plan.io/projects/pulp/issues/new Thanks. David On Fri, Nov 8, 2019 at 10:20 PM

Re: [Pulp-list] Issues with using S3 storage when running pulp on Amazon EC2 (pulp3)

2019-11-09 Thread Mike DePaulo
I think that with Ansible syntax, you need to specify: AWS_DEFAULT_ACL: I am fairly certain the lack of any value at the end would get interpreted as Python None. - Mike On Sat, Nov 9, 2019 at 6:57 AM David Davis wrote: > You should be able to set aws_default_acl to null (ie

Re: [Pulp-list] Issues with using S3 storage when running pulp on Amazon EC2 (pulp3)

2019-11-09 Thread Dumont, Joey
I have tried '~', 'null' and '' (without the quotes), and they all get rendered as null. This leads to an issue with running the migrations when running the Ansible script. I opened an issue: https://pulp.plan.io/issues/5687 Maybe this should have gone in the pulp-ansible project? Cheers,

Re: [Pulp-list] Issues with using S3 storage when running pulp on Amazon EC2 (pulp3)

2019-11-09 Thread Mike DePaulo
Hmm, I'm not sure if this should be addressed via dynaconf somehow or via Ansible logic. For troubleshhooting purposes, we can bypass the Ansible part by modify the settings.py manually, after it gets written (for example, with a non-standard Ansible task you add.) -Mike On Sat, Nov 9, 2019,