Zum Hauptinhalt springen

STAGE Decommissioning

πŸ€– Generated with Claude Code

⚠️ Not yet reviewed

Co-Authored-By: Claude (noreply@anthropic.com)

The decision to retire the STAGE environment is made. Nothing has been removed yet: STAGE is still up and still deployed to, and the timing is not ours alone to set β€” three partner insurers use it, and each needs a resolution first.

This document records where that stands and what removal will involve. It becomes the decommissioning record once the work starts, in the shape of vudev-decommissioning.md.

FieldValue
EnvironmentSTAGE / Stage (ASPNETCORE_ENVIRONMENT=Stage)
StatusDecision made, not started
TargetEnd of 2026 β€” a goal, not a commitment; see below
Key Vaultat-tgca-tis-s-default (Together-Fachtest subscription, TIS-Secrets)
Enterprise App / Groupstage-apps / Stage-Applications
Hoststage.servicebytogether.at
API gatewayapi-stage.togethercca.com
Deployment groupstage.servicebytogether.at
Repository survey2026-08-25, across all repos under the source root

What has to happen first​

The blockers are external, which is why the target date is soft.

StakeholderWhere it stands
Generaliready to tackle the topic in autumn
VIGneeds a solution for the yearly Klappung
UNIQAnot yet discussed

Until all three have a replacement for whatever they use STAGE for, the environment stays. Treat end of 2026 as an intention: it depends on partners we do not control.

What removal will involve​

Nothing here is done. The list is taken from what VUDEV actually needed, which is the only proven checklist we have β€” the lesson from that retirement being that the Azure and server side is quick and the configuration cleanup is the long tail.

ItemStatus
Deployment pipelines and release stages targeting STAGE removed❌
Deployment group stage.servicebytogether.at and its agents removed❌
Key Vault at-tgca-tis-s-default deleted❌
Enterprise App stage-apps and group Stage-Applications deleted❌
Servers offline❌
DNS records stage.servicebytogether.at and api-stage.togethercca.com retired❌
Gateway route configuration for the STAGE context removed❌
Documentation in this repository updated❌
Stale configuration removed from the application repositories❌

Scale of the configuration cleanup​

Baseline at survey time (2026-08-25), excluding build output:

Count
appsettings.stage*.json and nlog.stage*.config files41, across 26 repositories
Configuration files referencing the Key Vault at-tgca-tis-s-default12, across 12 repositories

The repositories carrying the most are tis.volltextsuche (6), tis.gf.smr5 (4) and tis.gf.esign (3); the remaining 23 hold one or two each.

As with VUDEV, an AKV reference to a deleted vault has no fallback β€” an application started with ASPNETCORE_ENVIRONMENT=Stage after the vault is gone fails at start-up rather than degrading. Deleting the vault before the configuration is cleaned up is therefore safe only because nothing should still be starting in that environment; verify that rather than assume it.

Unlike VUDEV, STAGE is a first-class environment in the platform library: TisEnvironments.Stage and IsTisStage() in Tis.Hosting.Extensions. IsTisStage() also matches .NET's standard Staging, and it is used by consuming services β€” so removing it is a breaking API change for the NuGet package, not a cleanup. That decision is separate from retiring the servers and SHOULD be taken on its own merits.

Re-checking progress​

From the source root (all repositories side by side), excluding build output:

# files named after the environment (case-insensitive)
rg --files --glob-case-insensitive -g '*stage*' -g '!**/bin/**' -g '!**/obj/**'

# references to the Key Vault
rg -l 'at-tgca-tis-s-default' -g '!**/bin/**' -g '!**/obj/**'

# host names
rg -l 'stage\.servicebytogether\.at|api-stage\.togethercca\.com' -g '!**/bin/**' -g '!**/obj/**'

Related: together-on-premises.md for what the environment consists of, and ../secrets/README.md for the vault and service principal.