Important Update From Author - Jun 5th, 2020 about yum-s3-iam HOT 2 OPEN

Welcome back @seporaitis,

One of the major reason of the slowdown on my part is that I lost access to a proper test platform. Several PRs unfortunately were not backward compatible (e.g. #69 inverses the priority of configuration vs environment variables, #78 adds the dependency to boto3, etc..).

A few notes:

• Regarding the use of boto3, one of the advantages of the yum-s3-iam module for its users is that it does not have dependencies that are not typically part of the standard distributions. At the time RHEL6/CentOS6 did not have a boto3 package (and making one was not easy because of the dependencies). It's certainly an option, but it would limit the target to distributions that have a boto3 package (or put a significant burden on users of those that don't).
• Trying to support too many syntaxes for the URLs has made some parts of the code too complicated. It's not an easy problem either (hostname validation, user-friendliness, etc.).
• As you have probably seen, we relied on a blog entry as a tutorial, and that blog was deleted.

from yum-s3-iam.

Thank you for the detailed answer @mbrossard it is very helpful.

Re: testing environment. I have set-up a basic GitHub Workflow that builds the RPM. It is my first GW, and just runs make rpm on CentOS 6/7. Probably it can be improved further (I saw a mention of rpmlint while reacquainting myself with rpm/yum). Next week/end I'll look for setting up a testing environment that could run the tests and maybe even could do integration testing. My thoughts are towards setting up a separate AWS account under my personal organization, with some limited credentials and have secrets set-up in this repo, so that various cases could be tested using GitHub Workflow. S3 buckets are free and the price for a few megabytes - negligible. How did the previous testing platform look/work?

Re: boto3 - very good point. My thoughts now are somewhere between:

• vendoring full or part of boto, responsible for credentials;
• re-implement a simple version of credential retrieval, so that it matches what people expect from boto3;
• provide an option to plug-in boto3 as needed;
• keep it as is, but document the limitations and/or workarounds for various use-cases.

All carry trade-offs, so before I change anything I will try to establish a somewhat good enough CI setup.

from yum-s3-iam.