Repository navigation
fix(data-manager): register built-in maintenance targets - #816
Merged
Merged
Conversation
Medformatik
added
the
docker
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Coordinated application updates could fail during preparation with
Unregistered execution role/targets: Data Manager startup registered only four transit targets, while configuration fences carry the complete application closure. Register the release’s built-in service inventory and share that production registration with admission and native update tests. Role, signature, deadline and unknown-target checks remain unchanged.The real-PostgreSQL regression reproduces the original rejection before the fix and passes afterward. Seven focused cases pass across the full fence suite, native update wiring and admission checks; API/Data Manager types, runtime bundle build and formatting pass. Native graph/Docker effects remain synthetic. This fixes new built-in-service admissions; it neither replays an already-failed update nor claims its recovery is complete. No live cancellation or deployment was performed for this patch.
Release and upgrade impact
Product impact: operator-action
The fragment explains that blocked installations need the corrected Data Manager and supervised recovery of existing failed work before another attempt. Unknown community-service targets remain rejected.