Skip to content

Refactor metadata_manager to move to versions provider based model#244

Open
shiv-tyagi wants to merge 8 commits into
ArduPilot:mainfrom
shiv-tyagi:feat/manifest-provider
Open

Refactor metadata_manager to move to versions provider based model#244
shiv-tyagi wants to merge 8 commits into
ArduPilot:mainfrom
shiv-tyagi:feat/manifest-provider

Conversation

@shiv-tyagi

Copy link
Copy Markdown
Member

This PR refactors the versions manager to move to a versions provider based model.

We introduce three providers:-

  1. ManifestJson provider which parses manifest.json from the firmware server and list officially released versions on custom build server based on that. We are moving away from a release git tags based method, to make sure we are in sync with official firmware server and also make sure we have features.txt for all versions we have.
  2. A whitelisted-tags provider which pulls tags in repo of whitelisted forks and list them for building on the custom build server.
  3. remotes.json based provider to allow manually listing versions on custom build server by adding entries into the file.

I have tested this locally and it works good.

I will update #242 to use the same manifest json client we introduced in this PR to help listing the standard builds for a vehicle-version-release combination.

@shiv-tyagi shiv-tyagi changed the title Refactor metadata_manager to move to versions provider based model Refactor metadata_manager to move to versions provider based model Jul 11, 2026
@shiv-tyagi shiv-tyagi requested a review from peterbarker July 11, 2026 04:30
@shiv-tyagi shiv-tyagi force-pushed the feat/manifest-provider branch from 7ab3df1 to 23eb457 Compare July 11, 2026 04:59
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.

1 participant