[Backend] Metadata.File: implement generateUpdateMetadataCacheNotification (Backend.Edge.App support)#3797
Open
arindahills wants to merge 2 commits into
Open
Conversation
…ation File metadata returned the empty default, so the BackendEdge aggregator never received an apikey->edgeId cache and its edge-facing server never started (Cache.isInitialized gates on a non-empty map). Build the map from the loaded edges so File-metadata backends can run the aggregator without requiring Odoo. Signed-off-by: arindahills <arinda.hillary@gmail.com>
arindahills
force-pushed
the
pr/metadata-file-aggregator
branch
from
June 30, 2026 21:03
8759a4a to
c1edb5b
Compare
arindahills
changed the title
Contributor
|
@sfeilmeier Could you please help review this PR when you have a moment? It adds Metadata.File support for generating the UpdateMetadataCache notification, so Backend.Edge.App can get the apikey -> edgeId mapping when running with file-based metadata instead of Odoo. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When connecting Edges through the
Backend.Edge.Appaggregator (the supported architecture, see #3795 and #3818), the app needs the API-key to Edge-ID mapping from the central Backend's Metadata service.MetadataOdooandMetadataDummyimplementgenerateUpdateMetadataCacheNotification(), butMetadataFileinherited the empty default, so a File-metadata Backend cannot serve the aggregator (the cache never initializes and Edges are rejected).This implements it for
MetadataFile, mirroringMetadataOdoo/MetadataDummy, so deployments that use File-based Metadata (i.e. without running Odoo) can use the Backend.Edge.App aggregator.