Yes, I was planning to do the switch within the next days.

So, I just wanted to upgrade aws-cli from v1 to v2, but it turns out that upstream is now bundling botocore and s3transfer into the source code which is against the policy that we have in openSUSE (and most other Linux distributions).

https://github.com/aws/aws-cli/pull/6494

I will stay on v1 until I have verified that we can unbundle botocore and s3transfer again.

This has nothing to do with the license but how the world, i.e. openSUSE and most other distros are set up to track security issues. That is one reason distro packaging policies do generally not want dependent code to be bundled. While rpm has some features to declare such bundled code I do not think all the tracking code that looks for CVEs has evolved yet to handle the bundling.

If we unbundle, i.e. we pull the bundled dependencies back out of the source tree then we have to carry patches that handles the "import" statements, I have not looked at how much work that will end up being and we force the SDK, i.e. botocore onto the update schedule of aws-cli v2. Meaning if botocore moves forward and aws-cli does not we cannot provide a newer package of botocore either.

I am only aware of 1 feature that is in v2 that is not supported in v1, that's sso.

Last but not least those that absolutely feel neglected by us still building v1, can build their own package or pull form AWS and get v2.

Zeyad Kenawi (zekena) - over 1 year ago

Thanks for your thorough answer and effort to maintain this package. I'm a bit new to openSUSE so that's why I'm asking. Personally I think aws should take this responsibility of distributing the cli to different distros instead of using the bash script and forgetting about updating it forever.

I haven't checked on the current state of the upstream sources for a while. I can have a look and see if things have improved.

@guinuxbr what in the v2 version do you need that is missing?