-
Notifications
You must be signed in to change notification settings - Fork 103
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
[TUF autoupdater] Include arch in release file path and download file path #1195
[TUF autoupdater] Include arch in release file path and download file path #1195
Conversation
Waiting until we've published at least one osquery release (now that changes in #1149 have been merged) to merge this |
Sorry to ping on this, but is there any news of when this would be? We're looking to run this on linux/arm64 and it seems like it's so close! @RebeccaMahany 🙏 |
@jaredallard Apologies for the delay on the response, I missed this! I'll be getting this PR through today since we've had a new osquery release -- however, the larger issue #1149 is also tied to an in-progress autoupdate rewrite #954 that I anticipate taking a little bit more time. I'll get #954 updated so that it'll be easier to follow it/track the status. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems reasonable.
I think all the path generation is hard to follow. I don't have an easy suggestion for a fix, though. I think over in the MirrorTool library, that's probably why I ended up with the abstraction I did -- so the objects can generate their own paths. But I'm not sure to easily apply that here.
Relates to #1149, #954.