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

Keep track of last update data for each dependency #581

Open
renatav opened this issue Jan 17, 2025 · 0 comments
Open

Keep track of last update data for each dependency #581

renatav opened this issue Jan 17, 2025 · 0 comments

Comments

@renatav
Copy link
Collaborator

renatav commented Jan 17, 2025

When a repository is updated, create or update a target file for each child repository, containing: branch, commit and last update date and time. These files should be updated every time TAF repo update is run, even if there are no updates. By doing this, we create some sort of a lot of updates. See cross repository timestamp specification for more details.

All of these new target files should be placed in a new subdirectory inside targets. It should be easy to create a new role only responsible for signing these targets, although defining roles is outside of the scope of this issue.

Th question here is, how to handle someone running the updater and not having th signing keys.

@renatav renatav moved this to Todo in TAF Planning Jan 17, 2025
@renatav renatav added this to the TAF 1.0 milestone Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

1 participant