Repository navigation
Conversation
This branch has not been deployed
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
1 participant
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.
An explicitly enrolled engine could attach to the service's current revision while running stale local arguments. Require the emitted
saas_config_versionbefore making an attach request, then compare it with the service revision before starting the worker or constructing components. Missing, malformed and mismatched revisions leave admission closed.Stacks on #5516. Paired operator and legacy image-wrapper changes emit the response revision for explicit enrollment only. Enrollment remains disabled by default; this does not prove a configuration content hash, exact physical inverter identity or target readiness.
Validation: 32 control/service tests pass, including actual
PredBat.initializerefusing stale configuration before component construction. Pre-commit passes. Staged GitNexus analysis reports low risk across four expected files.