AWS CLI v2 Update Script
A small script to keep the AWS CLI v2 up to date, until AWS figures out how to distribute software properly.
Usage
usage: awscli-update [-h] [--version] [-n] [-q] [--no-sudo] [--prefix PREFIX]
optional arguments:
-h, --help show this help message and exit
--version show program's version number and exit
-n, --noop only compare versions but don't install
-q, --quiet only print error messages when updating
--sudo use sudo to install (e.g. when installing to /usr/local)
--prefix PREFIX install aws-cli in custom path (default is /usr/local)
Setup
python3 -m pip install awscli-update
Auto update
Linux
Assuming the awscli-update binary is installed in $HOME/.local/bin
(check the location on your machine by running which awscli-update),
you want to install the AWS CLI in $HOME/.local/bin and
you want to check for updates every hour,
run crontab -e and add following line
0 * * * * $HOME/.local/bin/awscli-update -q --prefix $HOME/.local
macOS
Assuming the awscli-update binary is installed in /opt/homebrew/bin
(check the location on your machine by running which awscli-update),
you want to install the AWS CLI in /opt/homebrew/bin and
you want to check for updates every hour,
run crontab -e and add following line
PATH=$PATH:/usr/sbin
0 * * * * /opt/homebrew/bin/awscli-update -q --prefix /opt/homebrew
General things
If you want to check for updates more/less often or at specific times, check this editor for cron expressions.
Development
- Create venv (
python3 -m venv venv) - Start venv (
source venv/bin/activate) - Install dependencies (
python3 -m pip install setuptools wheel twine versioneer) - Install requirements (
python3 -m pip install -r requirements.txt) - Build local dist (
python3 setup.py develop --user)
Deployment
- Build dist (
python3 setup.py sdist bdist_wheel) - Deploy (
twine upload dist/*)
Metadata
Release files for awscli-update 0.1.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| awscli-update-0.1.12.tar.gz | 23.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| awscli_update-0.1.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.2 kB
Release files / awscli-update-0.1.12.tar.gz
| Download URL | awscli-update-0.1.12.tar.gz |
|---|---|
| Size | 23.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b84cabb66b630d7011a94405a441eb9cb1577b9cb7cce97d65d8d26334147145
|
|
BLAKE2b-256 checksum How to use checksums |
f9dbf7e7ba72f9cbd638160a55a6eae3ddc05c2fcddadb452ae38ccb393459c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.8.10
|
Release files / awscli_update-0.1.12-py3-none-any.whl
| Download URL | awscli_update-0.1.12-py3-none-any.whl |
|---|---|
| Size | 12.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a9cfaa644ae4ebafdd3934f73deea0d55641dae79061f0e1d549f2c39f9df4aa
|
|
BLAKE2b-256 checksum How to use checksums |
4eeeca1682166ce710eb82f6d748245d74870277ce43f39a492acbb3670d0f28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.8.10
|
Security for awscli-update 0.1.12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.