-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FEAT: Automatic signature updates #202
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- refactored `./fido/update_signatures.py` to add clarity; - generated FIDO sig file now validates against `fido/config/fido-formats.xsd` + fixed inconsistency between FIDO sig schema and 'fido/prepare.py''s use of 'apple_uid' and `apple_uti`; - PRONOM HTTP methods in dedicated `./fido/pronom/http.py` module (this needs to get more methods or merging with the SOAP module); - added basic (hacky) catch for 404s when downloading test resources; - safer use of empty list default for `fido/prepare.py FormatInfo:__init__`.
- allow zero signature elements; and - ommitted for previous check in.
- Python 2 compatibility re-established; - Pydoc and line spacing for CI tests on Travis.
Signatures now compiled and hosted on a web based update site: - Site URL set in config. - Docker based update web app to host and serve signature information. - FIDO CLI arguments `-sigs check` and `-sigs update` control automatic signature updates. This was implemented by: - implementing a REST service for FIDO signatures in `fido.signatures`; + simple flask REST app that parses a static dir/file structure; + endpoint to list versions; + endpoint that identifies latest version; + endpoints to download sig file collateral by version and `latest` for signature updates; + added resources for legacy format and container signatures; - adding simple REST client functionality to FIDO CLI: + `-sigs check` compares configured PRONOM sig version with REST latest and indicates if an update is required; + `-sigs update` pulls the latest version if the installed version is stale and updates the conf file as required;
carlwilson
added
feature
New functionality to be developed
P1
High priority issues to be scheduled in the upcoming release
labels
Apr 20, 2021
This was
linked to
issues
Apr 20, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signatures now compiled and hosted on a web based update site:
-sigs check
and-sigs update
control automatic signature updates.This was implemented by:
fido.signatures
;latest
for signature updates;-sigs check
compares configured PRONOM sig version with REST latest and indicates if an update is required;-sigs update
pulls the latest version if the installed version is stale and updates the conf file as required.