This testing is much needed, so I'm glad to hear it's progressing. Thank you for organizing. I put some questions inline. +1 to prioritizing it until it's in place.
On Mon, Feb 17, 2020 at 3:47 PM David Davis <davidda...@redhat.com> wrote: > Recently we discovered that S3 support was broken in Pulp 3.1[0]. Since we > have at least one stakeholder using S3 in production, we've decided that we > need to make it easier to develop and test our code against S3. To that > end, we have filed an epic for this work and are looking for feedback: > > https://pulp.plan.io/issues/5961 > > A few highlights/questions: > - We plan to use minio since one of our team members has experience with it > - We'll add a plugin_template config value that will run the functional > tests against S3. I think this should probably be a daily cron job. > Do you mean minio hosting S3 or actually S3? - I think the pulp-devel role should always install and configure minio but > leave the settings commented out in /etc/pulp/settings.py. That way, we use > filesystem storage by default but developers don't have to recreate their > dev environments if they want to switch over to S3 quickly to test > something out. > This sounds great > > Feedback is welcome. > > [0] https://pulp.plan.io/issues/6154 > > David > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
