You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9595a12
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: infrastructure/README.md
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Before provisioning, it shows the target and asks permission for billable resour
39
39
40
40
The guided flow creates a tagged state resource group/account first, with shared-key authorization and anonymous blob access disabled, TLS, identity-based data access, versioning, and soft deletion. Its public network endpoint accepts requests from any network, but reading or changing state still requires Azure authentication and Blob data permissions. The wizard does not require an IP address, CIDR, or external IP lookup. These bootstrap resources remain outside application Terraform state and are never deleted by the normal application destroy command. Do not reuse this backend for unrelated installations.
41
41
42
-
If an earlier installer created an IP-restricted state account, the wizard verifies its ownership and authentication settings, then asks before switching to authenticated access without the network restriction. It verifies the resulting settings before using state storage. It will not override disabled public access, a network perimeter, or an account with different ownership or unsafe authentication settings. If your organization requires private networking, use an authorized deployment path rather than bypassing that policy.
42
+
If an earlier installer created an IP-restricted state account, the wizard verifies its ownership and authentication settings, then asks interactively before switching to authenticated access without the network restriction. Unattended runs refuse this change; `--approve-deployment` is not consent to remove network restrictions. It verifies the resulting settings before using state storage. It will not override disabled public access, a network perimeter, or an account with different ownership or unsafe authentication settings. If your organization requires private networking, use an authorized deployment path rather than bypassing that policy.
43
43
44
44
It then uses separate protected Terraform state files for the foundation, application, and temporary provisioning modules. Foundation resources include an ACR and an RBAC-enabled, purge-protected Key Vault. Passwords are generated independently and written to Key Vault using private temporary files, never command-line values. Existing credentials are reused, not silently rotated. The PostgreSQL administrator password still enters protected application Terraform state.
45
45
@@ -49,7 +49,13 @@ The final release stops old revisions, runs migrations and schedule setup, start
49
49
50
50
### Saved configuration and repeat runs
51
51
52
-
By default, non-secret choices are saved in ignored `infrastructure/.local/installation.json`, with private generated inputs and Terraform working directories under `.local/INSTALLATION_NAME/`. Keep these files private and preserve the configuration for later releases. Start from [`installation.example.json`](installation.example.json) if you prefer to fill out the JSON yourself. Real configuration files belong under the ignored `.local/` directory, not beside the tracked example. The root shortcut runs the wizard from `infrastructure/`, so relative `--config` paths are resolved from that directory.
52
+
By default, non-secret choices are saved in ignored `infrastructure/.local/installation.json`. Private generated inputs and Terraform working directories live beside the configuration in `INSTALLATION_NAME-TARGET_HASH/`. The hash identifies the cloud, normalized tenant and subscription IDs, installation name, region, and case-normalized app resource group. Interactive and unattended runs use the same path. Separate targets cannot share generated files; adjacent configurations for the same target share a local workspace writer lock in addition to the Azure leases.
53
+
54
+
Keep the configuration directory private and owned by the current user (0700). Existing generated files must be private regular files (0600), not symlinks or hard links. Setup refuses shared, untrusted, or redirected paths without changing their permissions or contents. Start from [`installation.example.json`](installation.example.json) if you prefer to fill out the JSON yourself. Real configuration files belong under the ignored `.local/` directory, not beside the tracked example. The root shortcut runs the wizard from `infrastructure/`, so relative `--config` paths are resolved from that directory.
55
+
56
+
An existing name-only workspace such as `.local/INSTALLATION_NAME/` blocks deployment before cloud changes. Do not delete it or start with empty state. After stopping prior local installer processes, independently verify the saved subscription, tenant, installation, owner, and backend state keys against the intended configuration. Preserve a private backup and move that verified workspace to the target-specific path printed by setup. Review its private inputs and Terraform backend before rerunning. A mismatch or ambiguous workspace needs manual recovery rather than automatic adoption. This local migration does not clear any cloud leases.
57
+
58
+
Updates preserve validated optional inputs already stored in the workspace's `installation.tfvars.json`: `runtime_secret_references`, PostgreSQL SKU and major version, backup retention, and the custom hostname/certificate pair. Runtime references must match the main module's environment-name and Key Vault rules and must not reference the migration credential. Other customizations or invalid inputs stop setup before cloud changes or input rewrites. Review changes to immutable infrastructure through the existing Terraform guards; retaining a setting is not approval to replace resources.
53
59
54
60
```sh
55
61
# Collect and save configuration without creating cloud resources.
@@ -65,7 +71,7 @@ npm run setup:server -- \
65
71
--non-interactive --approve-deployment
66
72
```
67
73
68
-
Non-interactive execution requires complete configuration and fails with instructions when a prerequisite requires human action. It does not answer missing configuration questions or escalate access. Interactive runs refuse to overwrite a saved installation with a different target or owner; use a new configuration file for another installation. Normal updates use the existing release orchestrator; the wizard never directly applies the full application configuration to an installed Hub.
74
+
Non-interactive execution requires complete configuration and a clean source checkout, and fails with instructions when a prerequisite requires human action. Deployment approval does not authorize publishing uncommitted source or changing state network restrictions. Rerun interactively for those separate decisions. It does not answer missing configuration questions or escalate access. Interactive runs refuse to overwrite a saved installation with a different target or owner; use a new configuration file for another installation. Tenant and subscription UUIDs are canonicalized to lowercase across configuration, drafts, discovery, and deployment. Normal updates use the existing release orchestrator; the wizard never directly applies the full application configuration to an installed Hub.
69
75
70
76
You can reopen the wizard while Hub is running, but a deployment or update is a maintenance-window operation, not a no-downtime rerun. It requires fresh approval before stopping old revisions and running setup. A failed attempt may have left Hub running with retained leases; those leases still require the [interrupted-installation recovery checks](#interrupted-installation). Restarting does not clear them or inherit permission to stop workloads.
71
77
@@ -103,7 +109,9 @@ OpenTelemetry records the run, its phases, and individual command or prompt step
103
109
104
110
Telemetry never contains configuration answers, resource names, command arguments, environment values, UI messages, command output, exception messages or stacks, credentials, or deployment consent. Command names come from a fixed catalog; unknown commands use a generic identifier. No collector, network export, or environment-driven remote exporter is enabled. Files remain until you remove them; they are separate from drafts, Terraform state, and cloud leases.
105
111
106
-
Failed commands show their actual stderr to the local operator, limited to 64 KiB with terminal-control sequences removed. Those details may be sensitive: review them locally before sharing terminal captures. Successful command output is returned only to the caller, including token and secret lookups, and is not automatically printed. Neither successful output nor failed diagnostics enter telemetry or drafts.
112
+
Failed commands report a safe operation label and exit status by default, including in unattended output. Raw stderr is held privately in memory, limited to 64 KiB with terminal-control sequences removed. It is shown only after an interactive **Show full error details** choice in a supported recovery menu. Those details may be sensitive: review them locally before sharing terminal captures. Successful command output is returned only to the caller, including token and secret lookups, and is not automatically printed. Neither successful output nor failed diagnostics enter telemetry or drafts.
113
+
114
+
On cancellation or output-limit termination, setup signals the owned command process group and waits for its exit or bounded kill escalation even if the direct child exits first. If signalling or inspection fails, it reports a cleanup failure rather than claiming work stopped. Verify that owned commands and descendants have stopped before retrying.
107
115
108
116
The serialized release tool keeps raw child errors and output private because they can contain credentials or lease IDs. Its errors identify the failed operation through the shared static command catalog and include a nonzero exit code when available.
"Changing the existing state account's network restriction requires separate interactive consent. Rerun setup interactively; deployment approval does not authorize this change. Account network settings were not changed.",
121
+
)
118
122
if(
119
123
!(awaitui.confirm(
120
124
`State account ${names.stateAccount} restricts network access. Remove its network restriction and use Azure authentication and Blob data permissions instead? Shared-key and anonymous access will remain disabled.`,
@@ -209,7 +213,7 @@ export async function prepareBackend(context: AzureInstallation) {
"Unattended image publication requires a clean source checkout. Commit or remove the intended changes, or rerun interactively for separate working-tree consent. Deployment approval does not authorize dirty-source publication.",
0 commit comments