Repository navigation
feat(configurator): archive and delete unused application templates - #133
Merged
Merged
Conversation
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
October 22, 2026 06:45
12 of 22 tasks
lweberru
added a commit
that referenced
this pull request
Oct 22, 2026
Application Plan failures currently show only `plan_failed`: the UI exposes execution logs only for Apply, and immutable Application report storage accepts the first startup snapshot but rejects every changed progress/failure snapshot. This change exposes requester-only Plan/Drift/Destroy logs and enables redacted Application progress publication. Migration 063 permits only output ciphertext/hash/truncation updates during the existing exact-bound active dispatch. All three report paths retain session, delegation, claim, ticket and dispatch authorization; artifact/recovery conflicts, binding metadata and completed records stay immutable. Existing stored snapshots and customer State are preserved. A newer failed Destroy Plan now selects its own diagnostics instead of an older Destroy Apply's logs. English/German user and execution documentation describes the behavior. This repairs proven diagnostic blockers. It does **not** claim to resolve or qualify the underlying Corporate OpenTofu failure, whose later output was rejected and cannot be reconstructed from its first stored snapshot. No customer Plan/Apply or deployment was performed. Validation: - Full `npm run check`: 1,000 tests passed, 71 environment-gated tests skipped; build/typecheck/lint/Assistant contract checks passed. - Real isolated PostgreSQL identity/Application suite: 51/51, including repeated/idempotent output for nondelegated Plan, delegated Plan and delegated Apply, changing truncation, requester-only reads, direct runtime write denial, immutable artifact/metadata and terminal output. - Worker progress tests cover both brokers, publication failure/recovery, redaction and cleanup; a failed Application Plan retains its diagnostic and uploads no executable artifact. - Complete organization/Application browser suite: 112/112 desktop/mobile cases passed, including EN/DE Plan failure output, existing Apply/Drift/Destroy flows, and a new failed Destroy Plan after an earlier Apply. - Independent code/security review completed; reported Destroy retry-Plan selection edge fixed and regression-tested. - Combined with #133 in a temporary local merge: build/typecheck, PostgreSQL 51/51 and targeted desktop/mobile catalogue/diagnostics 14/14 passed; merge preview was conflict-free and discarded afterward. Scope: hosted Public/Corporate Application execution diagnostics; no native Accelerator input changes, production operation or customer infrastructure Apply. Merge is not deployment approval.
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.
Retired Application Landing Zone template versions currently remain mixed into the active catalogue. Move them to a separate Platform Engineer archive and allow explicitly confirmed deletion only when that version has never been ordered.
Deletion removes an unused retired version from the UI while retaining immutable publication/deletion evidence and version numbers. The server rechecks tenant/session/role and serializes deletion with ordering and retirement; deleted or archived historical orders permanently prevent deletion. Existing orders and State bindings remain intact. Both locales and the English/German user and architecture documentation describe the behavior.
Validation:
npm run check: 998 passed, 71 environment-gated tests skipped.git diff --checkpassed.No cloud Plan/Apply, merge or deployment was performed. Corporate Plan failure diagnosis is handled separately; this change does not claim to fix it.