openstack-image-manager
openstack-image-manager copied to clipboard
Easily manage and keep up to date a large number of images on an OpenStack environment
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/osism/openstack-image-manager). ## Open The following updates have all...
## Base PullRequest default branch (https://github.com/osism/openstack-image-manager/tree/main) ## Command results Details: add path ```Shell /home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin ``` tox -e update -- --dry-run ```Shell update: install_deps> python -I -m pip install -r requirements.txt...
There seems to be no real reason to have a separate script for updating image versions. This may as well be integrated into the main script.
Mirroring of images is specific to SCS environment. Other environments might not want that - so an option to disable mirroring would be nice.
Related to https://github.com/osism/issues/issues/913 Do not forget to add some marker to identify images that should be handled by the mirror.py script.
There are many unnecessary roundtrips in `manage.py`: - Each time an image is uploaded, the whole list of images is retrieved anew, instead of just adding the newly uploaded image...
Variable names that mask common global names should be avoided, such as - property - file - format - str etc.
Use the new 'verify_checksum' hash value in the yaml files to verify the image integrity after it has been successfully imported. Show a warning, if either the hash algorithm or...
Closes osism/openstack-image-manager#663
Apparently, the openstack-image-manager uses a library for extracting archives, namely `patool`, which is under GPLv3. As far as I understand, the image manager then is regarded as a work derived...