Repository navigation
feat(configurator): enable Public and Corporate application orders - #131
Merged
Merged
Conversation
Review source hashes for the immutable platform Runner pin, retain the existing governance assertions, and verify non-empty folder descriptions are rejected. Run the complete native Plan/Application/governance contract in PR validation before release packaging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
12 of 22 tasks
lweberru
marked this pull request as ready for review
October 21, 2026 16:39
lweberru
requested review from
BackInBash,
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
October 21, 2026 16:39
This was referenced Oct 21, 2026
lweberru
added a commit
that referenced
this pull request
Oct 21, 2026
…#132) The qualified Dev release on merged #131 passed all 118 repeated live Assistant cases and the 13-step continuous journey, then stopped before deployment because the local Runner package-identity test exceeded Vitest's default 5-second budget. The failed source-bound run remains recorded: https://github.com/stackitcloud/stackit-landing-zone/actions/runs/39650742104 . Give the local Runner test file a bounded 30-second test budget. These cases copy/hash the real Node runtime and perform multiple engine probes, each of which retains its existing 10-second production deadline. Assertions, source/artifact checks, model oracles and all production timeouts are unchanged. The test remains part of the ordinary CI and qualified release checks; there is no retry or skip. Also clarify the confirmed Namespace boundary in the English/German user guide and execution reference: Accelerator Namespace services have always targeted Platform Kubernetes only. They are excluded from Application project ordering; namespaces in a cluster within an Application Landing Zone belong to its workload. Private/SNA Platform Kubernetes remains deferred under #37. Possible much later Building Blocks layered on Application Landing Zones are a separate product decision, not an acceptance dependency for current Public/Corporate project ordering. Validation: `npm run check` passes (lint/types/build and 997 unit tests; 71 environment-gated skips); `git diff --check` passes. Public Dev health/access checks pass and deployed asset hashes are unchanged, confirming the failed release did not deploy. No customer infrastructure operation was performed. The Dev-release authorization already exists; after review/merge, a fresh qualified source-bound release is required. Related: #93, #37; follows #131. Final GitHub acceptance on `67bb5daa28bb699ccb6c00ac179cc3a8b7ea0a2c`: all applicable checks pass, including the complete Application/native/database suites and 312 desktop/mobile browser cases: https://github.com/stackitcloud/stackit-landing-zone/actions/runs/39654012523 . The unchanged native scope detector correctly skips native root-only jobs because no native Terraform sources changed. Protected main still requires independent review before merge.
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.
Application Owners can publish and order Corporate templates or Public templates without a network, but planning rejects them with an obsolete Public/local-network-only MVP guard. The Application Runner also still packages a source from before project-qualified bucket naming.
Pin the Application package to the reviewed native source
9e7fb46c329aca32e878ce1f0ea3b944ea240354and qualify Public projects with optional local networking and Corporate projects bound to the approved SNA target. Migration 061 extends the exact source allowlists for job grants, tickets and delegated dispatch. Existing template versions, orders, State keys, backend delegations and saved-plan approvals remain unchanged; using the new source requires a new publication/order, never silent rebinding.Show scope limitations before execution, explain personal organization proof when the applied-platform list is empty, keep configuration selection available in publication, and surface concrete configuration validation errors. Correct the publication notice and bilingual documentation: compiler responses reporting
executionEnabled: falsedo not mean the separately enabled Runner runtime is disabled. Unsupported direct-policy orders are stored without attempting an automatic unsupported Plan.Validation:
npm run check: lint/types/build pass; 997 unit tests pass, 71 environment-gated skips.Related to #93; this does not close its remaining live acceptance, quota and upgrade criteria. Namespace services and symbolic Observability network-ACL bindings remain blocked. No deployment, customer cloud Plan/Apply or production operation was performed. Runtime Dev Application execution was inspected read-only and is already enabled; no operator flag was changed.
Final GitHub acceptance on
3047e05fa75cc41a13e9fa994b81b41ef6167031: all applicable checks pass, including the complete native contracts, isolated database suite and full desktop/mobile browser suite in Configurator CI. Native root-only jobs are correctly skipped by the unchanged scope detector because this PR changes Configurator integration, not native Terraform sources. PR is ready for independent review; protected main still requires review.