Repository navigation
feat: add Application Git and database coordination for managed State - #274
Merged
Merged
Conversation
lweberru
marked this pull request as ready for review
November 18, 2026 13:02
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
November 18, 2026 13:02
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.
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.
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 source2b581f23dd40ccd4425e5e9efd93fb2c44cc8f8a; existing published versions, orders and State identities are preserved.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:
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.e7cfd5ee42057854baed448ac4a1da838bf802db989efb86444c2fa780251164, suite hash9694d710e54b08ac20a2d40f2fc0b403c7c0c60c0db89c9cad759bc6c7ea5791. Both model roles use the application defaults. The two new Git setup/history cases also passed twice individually.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:
343aa89a8bbf7c31c5891b6081628078b6a0eee9.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.92bc9dac3cb4c1ccac2a835f0405d6be330363cec8164e3bb4fe569f706ce232; suite SHA-256:ceea8b581f812d39324e5f8479f29e9504e0a05ddcd26e2bffddf902d86659eb.No customer infrastructure Plan/Apply was executed by this rollout.