Skip to content
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

Making the process of updating metadata a little bit more flexible #815

Conversation

renatav
Copy link

@renatav renatav commented Dec 21, 2018

Description of the changes being introduced by the pull request:

client/updater.py was slightly refactored in order to make the process of updating metadata files a bit more flexible. This flexibility is only related to how the files are downloaded and does not impact validation. Finding mirrors and the actual download were moved to a so-called handler class.
With that change, it is possible to implement the majority of the updater which would use a git repository to store metadata files. An example of that implementation can be seen here.

Please verify and check that the pull request fulfills the following
requirements
:

  • The code follows the Code Style Guidelines
  • Tests have been added for the bug fix or new feature
  • Docs have been added for the bug fix or new feature

In order to make the process of downloading metadata files more flexible,
finding mirrors and the actual download were moved to a so-called handler class.
With that change, it is possible to load a file from a specific commit of
a git repository for example

Signed-off-by: Renata <vrenata8@gmail.com>
@renatav renatav force-pushed the updater_metadata_refactoring branch 2 times, most recently from e22e73c to 690b686 Compare March 19, 2019 12:23
@@ -391,6 +391,7 @@ def status(self):
self._log_status(self.project_name, signable, self.repository_name)

except securesystemslib.exceptions.Error as e:
# pylint: disable=unsubscriptable-object
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OT: This seems to be the reason why the current TUF@develop build is failing. IMO it should be fixed in a separate PR. Such a fix should probably also evaluate, whether pylint has a point here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#839 resolves this issue. (Sorry, folks.)

@renatav renatav force-pushed the updater_metadata_refactoring branch from 3298bce to 6de2740 Compare April 22, 2019 16:12
@joshuagl
Copy link
Member

Thank you for the contribution. Due to imminent refactor efforts this code is unlikely to merge, but we would very much welcome your input and engagement on our refactor plans.

@joshuagl joshuagl closed this Sep 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants