Skip to content

It's hard to package version 2 of aws-cli #5282

Closed
@graywolf-at-work

Description

@graywolf-at-work

Confirm by changing [ ] to [x] below:

Issue is about usage on:

  • Service API : I want to do X using Y service, what should I do?
  • CLI : passing arguments or cli configurations.
  • Other/Not sure.

Platform/OS/Hardware/Device
Archlinux, but this is platform-agnostic issue.

Describe the question
Currently it is really hard to track the aws-cli v2 for the purpose of packaging it. My steps basically are

git checkout TAG
pip install -r requirements.txt
pip install .

and that works fine until there is an update to botocore, since at that
point it will stop being possible to install previous tags. I would like you
to consider making the dev versions in botocore actual tags, so that the
installation will work even after you release new version.

The exact same thing happend yeasterday, there was new botocore released
but 2.0.20 was not (yet), so in that interval it was just not possible to install
it.

But my python-fu is not the strongest, maybe there are flags to pip that would
solve this?

Logs/output
Get full traceback and error logs by adding --debug to the command.

N/A

Metadata

Metadata

Labels

feature-requestA feature should be added or improved.installationp2This is a standard priority issueresponse-requestedWaiting on additional info and feedback. Will move to "closing-soon" in 7 days.v2

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions