Skip to content

feat: add Application Git and database coordination for managed State - #274

Merged
lweberru merged 7 commits into
mainfrom
feat/application-git-state-serialization
Nov 18, 2026
Merged

lweberru merged 7 commits into
mainfrom
feat/application-git-state-serialization

Conversation

@lweberru

@lweberru lweberru commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

STACKIT EU01 Object Storage does not enforce the conditional writes required by native S3 lockfiles. Configurator executions now coordinate in their shared PostgreSQL database. Application Landing Zones can also offer an optional dedicated managed Git service, independently of central platform Git.

  • Add native git = { enabled, flavor, acl } inputs and instance-ID outputs without a Configurator dependency. Templates expose fixed or bounded order choices. New Git templates use immutable native source 2b581f23dd40ccd4425e5e9efd93fb2c44cc8f8a; existing published versions, orders and State identities are preserved.
  • Cover publication, compilation, upgrades and recovery. Git defaults to disabled and requires explicit source CIDRs. Git10/Git100 limits apply per instance; Corporate/SNA placement does not make managed Git private. Provider 0.114.0 replaces instances on flavor or ACL changes, which the non-destructive Application upgrade guard rejects. Repository migration and Git-user onboarding remain separate.
  • Atomically bind each physical State path to one logical managed State, including concurrent aliases across workspaces. Claimed failed/cancelled executions remain exclusive until verified cleanup or reviewed recovery. Ticket expiry no longer permits competing drift/destroy operations. Preserve correction of previously reconciled bootstrap checkpoints from the preceding platform source.
  • Document organizational single-writer operation for standalone CLI/pipelines and explicitly disable ineffective lockfile exclusion in the example. The Configurator retains its descriptor for compatibility but coordinates through database reservations. Independent writers or separate Configurator databases are outside that coordination. Native conditional-write support is requested without an announced delivery date.
  • Provide bilingual guidance, template UI and source-bound Assistant regressions. For documented architecture boundaries, the model selects evidence-backed closed facts; the application renders their reviewed meaning in English/German. Require actual HA patches for existing appliances with known prerequisites, preserving native IP defaults and keeping business follow-ups. Verify Audit advice against the current question before choosing component information or concrete Plan/Apply-impact guidance. Verify informational classifications against the current setup request using the shared Editor service registry; missing choices lead to typed follow-ups rather than a field overview. Resolve static Editor follow-ups from the current user language, independently of earlier assistant replies. Broader guided consultation remains separate in draft feat(configurator): share service guidance and described Assistant catalogue choices #273.

Migration 098 backfills physical State ownership. Conflicting historical aliases stop migration for operator review rather than silently choosing a writer. No State objects, keys or saved plans are migrated.

Validation:

  • Local app checks: 1,887 passed, 81 default skips. The separately enabled PostgreSQL platform suite passes all 67 tests.
  • Full PostgreSQL integration suite: 225 passed, one skipped. Parallel physical-State admission, tenant boundaries, template upgrades and previous-source checkpoint correction are covered.
  • Native root tests (54), Application/module/compiler contracts, all eight supported execution sources, common contracts (21), HCL adapter and requalified governance contracts (4) pass.
  • GitHub CI: all 16 checks pass on final head 6b634626ca814885551f889bc21f4313da948e1f, including native contracts, database migrations, the real HTTP/PostgreSQL upgrade journey and desktop/mobile browser acceptance. The 20 targeted template browser tests also passed locally.
  • Final source-bound real-model qualification: 224/224 cases passed (112 cases, each repeated twice), plus the 14/14 continuous multi-topic journey, on knowledge hash e7cfd5ee42057854baed448ac4a1da838bf802db989efb86444c2fa780251164, suite hash 9694d710e54b08ac20a2d40f2fc0b403c7c0c60c0db89c9cad759bc6c7ea5791. Both model roles use the application defaults. The two new Git setup/history cases also passed twice individually.
  • Qualification found and corrected missing Firewall HA proposals, Audit Plan/Apply advice misrouting, and Git setup requests misclassified as information, including history-dependent language drift. Earlier failed receipts are retained; oracles were not relaxed. These results qualify this PR's final source, not the separate broader consultation changes in draft feat(configurator): share service guidance and described Assistant catalogue choices #273.

No deployment, release or customer Apply was performed.

Closes #262.

Rollout verification

Merged with the user-authorized admin merge and deployed successfully on 2026-11-18:

  • Combined release commit: 343aa89a8bbf7c31c5891b6081628078b6a0eee9.
  • Dev build and deployment: successful, including 256/256 repeated real-model checks, 14/14 continuous-dialogue steps, application/database/browser/native-runner verification and runtime connection tests. The public page and STACKIT-authenticated health endpoint pass.
  • Production release and deployment: successful. v2.2.0 reuses that exact immutable Dev build, with mode=qualified. All three production web/API replicas, public TLS/authentication/tenant boundary, service connections and isolated Runner checks pass. Independent post-deploy page and health checks also pass.
  • Knowledge SHA-256: 92bc9dac3cb4c1ccac2a835f0405d6be330363cec8164e3bb4fe569f706ce232; suite SHA-256: ceea8b581f812d39324e5f8479f29e9504e0a05ddcd26e2bffddf902d86659eb.
  • No model HTTP 400 occurred in the current local or release qualification. The historical intermittent issue fix(assistant): structured-output HTTP 400 and incorrect execution-upgrade routing #225 remains open; these passing receipts do not establish its root cause or guarantee that it cannot recur.

No customer infrastructure Plan/Apply was executed by this rollout.

@lweberru
lweberru marked this pull request as ready for review November 18, 2026 13:02
@lweberru
lweberru merged commit c9f4252 into main Nov 18, 2026
16 checks passed
@lweberru
lweberru deleted the feat/application-git-state-serialization branch November 18, 2026 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(state): STACKIT EU01 ignores conditional PutObject, invalidating native S3 state locking

1 participant