Repository navigation
fix(recovery): accept actual STACKIT CF instance identifiers - #150
Merged
Merged
Conversation
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
October 24, 2026 09:13
10 of 13 tasks
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
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.
The new Dev recovery hold rejected the real STACKIT web process before any native interruption: this foundation emits
CF_INSTANCE_GUIDin shortened hexadecimal8-4-4-4-4form. The real CF preflight confirmed that every other app, space, origin, route and web-process guard passed. Replacing only the runtime-instance value with a generated UUID made the original guard accept, identifying the precise mismatch.Accept the observed shortened form and full
8-4-4-4-12GUIDs only for this opaque runtime-instance field. Actual app, space and disposable-order IDs still require UUIDs; the fixed Dev origin/foundation, exact bindings, route-free web process and expiry checks are unchanged. Task, missing-process and foreign app/space contexts remain excluded. Add explicit positive/negative format regressions and update both operator runbooks.Validation: full app check (1,060 passed; 74 environment-gated skipped), 11 focused worker tests including real pinned OpenTofu hold/resume/interruption, and 27 recovery-controller tests. Existing failed runtime preflight receipts are retained. The corrected candidate also passed in a credential-free disposable CF web app using actual, unmodified CF metadata: real native-process stop, automatic 30-second continuation, successful synthetic Plan and fixture cleanup. The temporary app was deleted. This candidate evidence does not replace verifying the final release or the actual hosted-job interruption, which remains unqualified under #95.