Skip to content

v0.7.0

Choose a tag to compare

@kayladouglas23 kayladouglas23 released this 30 Oct 21:04
· 1 commit to main since this release

Upgrade: CredsStack, WebStack; NetworkStack and every ConnectorStack if you run the private network.

  • Private network: a failed relay map refresh no longer leaves a site without relays (#83). Headscale v0.26.1 refreshes the relay (DERP) map from controlplane.tailscale.com every 24 hours and, when one download fails, sends every node an empty map until the next refresh, so users could not connect for up to a day. Each control-server start now saves the live map to the site's EFS folder (a failed download keeps the previous copy and never stops the task), and Headscale merges that copy with the live map region by region (the live map wins per region), so a failed refresh still leaves every region of the copy. A region Tailscale removes stays in the map until the next control-server start. Connectors get an ECS health check: one that has reported "could not connect to the ... relay server" for about five minutes is replaced automatically, which is what a stuck connector needed after the map came back. With an alert topic, the new DerpMapLoadFailed alarm fires when a control server logs Could not load DERP map. Upgrade: NetworkStack (manual, --exclusively; restarts each control server once) and every ConnectorStack (restarts each connector once).

  • Sign-in: turning on an authenticator app now makes this device remember password as its sign-in method, so the login page stops jumping to a passkey or email code that Cognito no longer offers that user. The Passkeys dialog and the "Only your password is offered" notice now say an authenticator limits sign-in to password + code. Upgrade: WebStack.

  • Users: the People list is sorted by email A to Z, and a Sort dropdown in the toolbar switches it to email Z to A or to last seen (most recent first, or longest ago first; someone who never signed in counts as the oldest) (#80). The sort runs in the browser after search and filters; a reload starts at A to Z again. Upgrade: WebStack.

  • roleSessionName: "userId" | "email" (#65) chooses how a vended role's STS session is named, which is what the target account's console and CloudTrail show as the federated user (<Role>/<session>). userId (the default, and every deployment's behaviour so far) keeps creds-<Cognito sub>; email names the session after the caller — a person's email, a personal access token's owner's email, a service user's registry name — so a team in the target account can see who made a change without asking an Infra Client admin to look the sub up. Characters STS does not allow become _; an empty or over-long name falls back to creds-<sub>. The admin Roles page's session-length Test follows the same policy (test-<sub> or the admin's email). Role trust is unchanged: the signed token still pins the caller's sub. Sessions vended before the switch keep the UUID in CloudTrail. Upgrade: CredsStack.

  • The StaleConnectors alarm no longer fires for a connector node that a trusted online connector in the same account and VPC has replaced (#70). Fargate retires connector tasks for platform patching every few days, and every upgrade that changes the connector task definition re-registers the connector; the old node stayed in the stale count, and the alarm with it, until the 24-hour prune. The reconciler now counts a node as stale only when its account and VPC has no online trusted connector, lists a replaced node as supersededConnectors (the EMF log line, the reconciled log and the site's status row) and still prunes it 24 hours after it went offline. The alarm's metric, threshold and period are unchanged; its description names the new rule. Upgrade: NetworkStack (manual, --exclusively).

  • Private network: a user's first connect to a site reaches their granted resources within seconds (#76). The reconciler leaves out users Headscale does not know yet, and the device minter creates that user on the first enrollment, so the rules waited for the next scheduled pass (up to 5 minutes). The device minter now starts a pass (an async invoke of <prefix>-acl-reconciler, named by its new NETWORK_RECONCILER_FN_NAME variable) whenever it creates a Headscale user; a failed start is logged as a warning and the key is still returned. Later mints start nothing. Upgrade: NetworkStack (manual, --exclusively).

  • Private network: Security Hub ELB.17 passes again for the Headscale ALB listener (#78). AWS removed ELBSecurityPolicy-TLS13-1-2-Res-2021-06 from the control's accepted policies, so existing deployments started failing it with no change on our side. The listener now uses ELBSecurityPolicy-TLS13-1-2-Res-PQ-2025-09: the same TLS 1.2/1.3 protocols and ciphers plus hybrid post-quantum key exchange, so no client loses access; the listener is updated in place. Upgrade: NetworkStack (manual, --exclusively).

  • The credential issuer's KMS signing keys carry an alias per key version, alias/<prefix>-oidc-signing-v<N>, so the KMS console names them (#76). The keys and their policies are unchanged. Upgrade: CredsStack.

  • Desktop (Windows): the tray row Update … available · Open download page opens https://github.com/FNTIO/aws-infrastructure-client/releases/latest; since 0.5.0 it opened github.com/undefined/undefined/…, because the packaged package.json has no build block to read the feed from (#69). macOS, which downloads and installs from the tray, was not affected.

  • Desktop: a saved deployment that is waiting for the network or unreachable shows its status as a chip beside its name (no network in amber, unreachable in red) instead of a suffix on the name; the name ellipsizes, the chip never does, so the status stays readable for any name length (#72). Hover text, click-to-retry and ✕ are unchanged.

  • Desktop: About Infra Client and Check for Updates… in the app menu (#71). On macOS the check sits below About in the app menu, which keeps every default entry; Windows and Linux get a Help menu with both, so Windows shows the installed version for the first time. The tray has the check too while no update is pending. A manual check always answers: the latest version, a restart on macOS once the update is downloaded, the Release page on Windows, or the error. The automatic checks stay silent, as before.

Full changelog: CHANGELOG.md · npm: @fntio/infra-client