Skip to content

cloudfall 0.8.0rc27

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 13 Nov 15:42
· 215 commits to main since this release

Changes since v0.7.0:

Breaking

  • deploy --yes and migrate --yes on an application that declares approval: manual now need a person's approval of the release: without a cloudfall release approve record that counts (the same archive SHA-256, exactly the component's declared servers, not expired), deploy --yes exits 4 PRECONDITION with deployment_approval_missing before any playbook runs, naming the release approve command, and lists each record that doesn't count with digest_mismatch, servers_changed or expired. This hits every project that declares manual and deploys today, the example crm.yaml and every Render import included. Two ways out: keep manual and approve each release first (build it, run cloudfall release approve at a terminal, commit the record under decisions/releases/ when CI deploys, then deploy), or switch the application to approval: automatic when another gate, such as GitHub's required reviewers, is the real one. The deploy plan and result gain approval (policy, and for manual the status, the counting record's path, approver and expires_at or approved_at, the records that don't count and the command to run), deploy gains --approvals (default decisions/releases) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval, and cloudfall mcp serve binds the approvals folder (its own --approvals) so a deploy call can't name its own; an automatic application's deploy never reads the folder (#163)

Added

  • A Component can declare spec.buildTools (tool name to minimum version), spec.build (ordered steps, each a workingDirectory inside the packaged root, an argv command and an optional timeoutSeconds from 1 to 3600, default 900) and spec.artifact.include (relative paths the build produces); cloudfall config validate refuses a step whose command[0] is not in buildTools (component_build_tool_undeclared), an absolute or .. path, and buildTools or artifact without build. Validation only: artifact build does not run the steps yet. Components without build validate as before (#113)
  • cloudfall-engine artifact build runs a Component's declared spec.build steps on the controller before packaging: it checks every spec.buildTools entry is on PATH at its minimum version before cloning (artifact_build_tool_missing, artifact_build_tool_unsupported), runs each step in the clean checkout with only PATH, HOME, LANG, TMPDIR and CI=true in its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its own timeoutSeconds (artifact_build_step_failed), a missing include path (artifact_include_missing), an include path that leads out of the checkout through a symlink (artifact_include_outside_checkout) or a tracked file a step deleted (artifact_tracked_file_missing), packages the tracked files plus every spec.artifact.include path (a gitignored web/dist, say), and records the steps and tool versions as the new optional spec.build of the Artifact metadata. The command's time limit is now the clone time (1800 seconds) plus every declared step timeout, on the CLI and the SDK/MCP path alike; an explicit --timeout replaces it, and --timeout 0 still disables it. A Component without build is packaged as before (#115)
  • The converge_domains MCP tool takes an optional domain: given, domains.yml runs only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exits PRECONDITION (lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now records previousConfigurationSha256, the sha256 of the vhost file the run replaced, or null when none was there; receipts without it still load (#116)
  • cloudfall domains apply <domain> [--issue-certificate] [--yes] converges one Domain: domains.yml runs on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without --yes it exits 0 with a plan. --issue-certificate refuses a Domain with tls.mode: disabled, and first checks on the controller that the primary name and every alias resolve to the proxy server (PRECONDITION, domains_dns_unverified, naming each failing name); a proxied Domain skips the check (dnsCheck: "skipped-proxied"). With --yes it answers the receipt path under --deployments (#117)
  • cloudfall domains observe <domain> reads one Domain on its proxy server alone, through the new read-only domains-observe.yml: the vhost file and its sha256, the certificate's expiry, certbot.timer, and whether the vhost still matches the last receipt (receipt: null before the first). It changes nothing on the server or in the project, and a missing vhost exits 0. cloudfall mcp serve lists domains_apply (with its yes gate) and domains_observe as tools (#118)
  • Components: a release.command (with optional workingDirectory and timeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server of deployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes or current moves; it runs as the application's user with the component's env file loaded under systemd's EnvironmentFile= rules. A non-zero exit or a timeout fails the deploy with ENGINE_STEP_FAILED before any server switches, and a passing run is recorded as releaseCommand (server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119)
  • deploy without --yes shows the component's release command as release_command (its command, the working directory resolved under the new release directory, timeout_seconds and the release server), or null for a component without one, and says in would_run that it runs once on that server before any switch; the rollback plan of a component with a release command shows release_command_skipped: true, since a rollback never runs it (#120)
  • A PostgreSQL Service database may name an owner role and its passwordRef (environment, path, key in the secrets store) instead of an application, so a project of a server and its database alone validates; spec.postgresql.remoteAccess declares a listen address and the client networks allowed in. config validate refuses an entry with both or neither of application and owner, an owner without passwordRef or a passwordRef next to application, a reserved owner (service_database_owner_reserved), and a remoteAccess with no owner database, no firewall, the port already open, or a source of every address. Converging these declarations comes later: until then the PostgreSQL role refuses them before any task runs (#121)
  • services.yml converges a PostgreSQL database owned by a declared role: it creates the owner login role, sets its password from passwordRef as SCRAM-SHA-256 on every converge, and gives it the database; backups, the restore drill, and data copy (restoring as the owner, its receipt's spec.owner) cover it like any other database. Every path that runs services.yml (the converge_services MCP tool, the services step of cloudfall migrate, operator approve and operator run, and cloudfall-engine playbook run services.yml) reads the password from a --secrets-dir flag (default secrets) and stages it in a 0600 file in a private temp dir outside the project, removed after the run; the value is in no inventory, command line, Ansible output, answer, or receipt, and the answer's owned_roles names the reference, the key, and the value's SHA-256; operator approve records them as ownedRoles in the proposal receipt's outcome (an optional property) and operator run in each executed proposal's entry. A missing secrets file or key fails with PRECONDITION naming the expected path and key before any playbook runs (#122)
  • A PostgreSQL service with spec.postgresql.remoteAccess opens to its declared sources over TLS: services.yml sets listen_addresses = '127.0.0.1,<listenAddress>' and ssl = on with the Debian ssl-cert snakeoil pair (restarting the cluster), and writes one hostssl <database> <owner> <cidr> scram-sha-256 line per owned database and source between Cloudfall markers in pg_hba.conf, reloading only after pg_hba_file_rules reports no error; baseline.yml adds one ip saddr/ip6 saddr <cidr> tcp dport <port> accept rule per source, rendered as a cloudfall_firewall.allowedInbound entry with a new optional sources list. Removing remoteAccess resets the listener and removes the pg_hba.conf block and the firewall rule; databases named by application stay socket-only (#123)
  • cloudfall data copy takes a repeatable --source-schema NAME (and the data_copy MCP tool a source_schema list): the dump and restore copy only the named schemas, the empty-target check and the per-table row-count check read exactly those schemas, and the plan without --yes names them; a name that is empty, longer than 63 bytes, or holds a control character or a brace is refused as a usage error. Without it the dump is the whole database as in 0.7.0, and the checks now cover every non-system schema of the source instead of public only, so a row-count mismatch outside public now fails the copy. The DataMigrationReceipt gains spec.schemas (sorted) and a schema on each spec.tables[] entry beside table and rows (#124)
  • cloudfall data copy, and the data:<database> step of cloudfall migrate, run a preflight on the target host after the empty-target check and before pg_dump: it reads both catalogs and refuses a copy the target can't hold, with nothing dumped, the target untouched and no receipt, exiting PRECONDITION with code data_copy_preflight_refused and four lists in the error context, each item named: missingSchemas (a named schema the source lacks), extensions (one the selected schemas need, through pg_depend or by living in them, or every source extension but plpgsql without --source-schema, that the target's pg_available_extensions lacks), roles (a role a row-level security policy on a selected table names that the target's pg_roles lacks) and authReferences (a function or policy of the selected schemas that references auth. when auth isn't copied). The role writes the findings to <service>-<database>.preflight.json under --data-migrations, so the lists arrive whole. With --source-schema, pg_dump also gets one --extension per extension the schemas need (pg_dump 14 or later), and pg_restore now runs with --single-transaction, so a failed restore rolls back whole, writes no receipt, exits ENGINE_STEP_FAILED, and the next run passes the empty-target check (#125)
  • cloudfall migrate takes a repeatable --data-schema DATABASE=NAME beside --data DATABASE=PATH (and the migrate MCP tool a data_schema list): the data:<database> step copies only the named schemas, as data copy --source-schema does, and the plan names them. A --source-schema or --data-schema name must now match ^[a-z_][a-z0-9_]*$ and be at most 63 characters, and may be given once per copy; a name that doesn't, a repeated name, or a --data-schema for a database with no --data exits PRECONDITION (code data_copy_schema_invalid or migrate_data_schema_without_data) before any playbook runs, where a malformed name was a usage error and a repeat was silently dropped (#126)
  • A Domain can declare spec.routes, path routes that each either proxy to an upstream (address, port) or serve a component's release files (static: component, directory, optional spaFallback). cloudfall config validate refuses a Domain with both proxy.upstream and routes (domain_route_source_invalid), a path that doesn't start with / or uses characters outside letters, digits and ._~/-, or a static path without a trailing / (domain_route_path_invalid), a path declared twice (domain_route_path_duplicate), a path under /.well-known/acme-challenge (domain_route_path_reserved), a missing static component (resource_reference_missing) or one not deployed on the Domain's proxy.server (domain_route_component_not_on_proxy), and a directory or spaFallback that is absolute, climbs out with .., or, for directory, names the release root. Validation only: the domains playbook doesn't render routes yet and still refuses a Domain without proxy.upstream before any change. Domains with only proxy.upstream validate and render as before (#159)
  • cloudfall release approve <component> --release <release> records a person's approval of one built release as a ReleaseApproval (new release-approval.schema.json) under decisions/releases/: the application, component, release, archive SHA-256, git commit, servers, approver, approvedAt, expiresAt (--valid-for hours, 1 to 168, default 24) and via: terminal. It verifies the artifact first, refuses a component of an automatic application with release_approval_not_required, and writes the record only once a person typed the release id at a terminal; --yes never answers it, and it is no MCP tool. It deploys nothing (#160)
  • Components: a healthCheck of type: command (a required non-empty command argv, timeoutSeconds 1 to 300 and attempts 1 to 20, no other key) validates, and deploy, restart and rollback without --yes name the check and its command in their plan's wouldRun (#161)
  • cloudfall domains apply renders a Domain's spec.routes: a proxy route becomes a location that proxies to its upstream with the full request path, and a static route serves <installRoot>/current/<directory> of its component, answering spaFallback for an unknown path when it declares one and 404 when it doesn't. Without a / route, a path no route matches answers 404, not Nginx's default page. Locations render longest path first, whatever the declared order, where the single proxy location rendered before (the port 80 server without active TLS, the 443 server with it); the port 80 redirect and the ACME challenge location stay. The site role grants the Nginx worker (www-data) traverse-only access (POSIX ACL user:www-data:--x, installing acl) from the application root to the install root and its releases/, so it reads the release files but never shared/env/<component>.env, and a deploy or cloudfall rollback switches what a static route serves without re-running the domains playbook or reloading Nginx. The domains playbook's early check now refuses only a Domain with neither proxy.upstream nor routes. A Domain with only proxy.upstream renders a byte-identical vhost (#162)
  • Deploy: a component's healthCheck of type: command now gates deploy --yes. After the switch and the restart it runs on each server in a transient systemd unit cloudfall-health-<component>, as the application's user, in <installRoot>/current, with the service's env file and timeoutSeconds as its runtime limit, up to attempts times 3 seconds apart. When every attempt fails or times out, the previous release is restored (a first release is stopped), the deploy fails with ENGINE_STEP_FAILED naming the check and its exit code or timeout, and the release receipt is written with healthCheckPassed: false. Receipts of a command check carry healthCheck (command, attempts, exit code, timed out), never the command's output, which stays in the server's journal. The release receipt schema accepts healthCheckPassed: false only with a failed command healthCheck, and every receipt written before (#164)
  • restart, rollback and health run a component's type: command health check instead of refusing it: the same transient unit as deploy's gate, with its user, working directory, env file, timeout, attempts and redacted output. health reports unhealthy when the check exits non-zero or times out, a failed check fails restart or rollback without restoring anything, as an http check does, and none of them writes a release receipt. The check starts its unit as root, so health of such a component needs the inventory SSH account to become root, as restart and rollback already do; http and none checks are unchanged (#166)
  • cloudfall config upgrade: rewrites a project from the deprecated ServerType names to Baseline (moves server-types/ to baselines/, rewrites kind and spec.serverType), keeping comments, formatting and line endings; a second run changes nothing, and it refuses, changing nothing, a move onto an existing file or a file or folder reached through a symlink (upgrade_symlink) (#198)
  • audit checks the certificates a server's host requirements name (present, for the right names, more than 30 days left at the observation's time) from new certificates evidence inspect collects, and expects the logging gateway's firewall rule, so a deployed stack audits compliant (S-011)
  • cloudfall logging deploy provides the stack's mTLS material: each host makes its own key and a signing request (logging-requests.yml), the project CA signs the missing and due certificates, and they are delivered with the CA; certificates provided by hand are kept (S-011)
  • cloudfall logging deploy: deploy the declared LoggingStack after meeting its secret requirements; generated secrets are written to the store, an input secret that is missing stops the run (exit 4, INPUT_REQUIRED), and each stored secret is copied to its host path without overwriting a file already there; without --yes it shows the plan (S-011)
  • Logging collectors pin the gateway name to the backend's address in /etc/hosts (loopback on the backend itself), so the gateway needs no DNS record when the backend declares an IP (S-011)
  • The logging gateway's port opens on the backend's firewall to each remote collector's addresses only, rendered beside the remoteAccess rules and enforced by logging.yml; a remote collector with no IP behind a firewall fails config validate (logging_gateway_collector_unaddressed) (S-011)
  • LoggingStack: migration.mode: none for a host with no legacy agents; parallel still requires preserveLegacyAgents: true (S-011)
  • Logging roles check every package pin against the host's APT sources before installing or configuring anything, and stop naming the versions on offer when one is missing (S-011)
  • Certificate provider, controller side: a project CA per environment, kept sops-encrypted under secrets/<environment>/pki/, that signs host requests for exactly the names and usage a requirement grants (S-011)
  • cloudfall requirements show: the volumes, ports, secrets, certificates, DNS names and package pins each declared LoggingStack needs from its servers, by server (S-011)
  • cloudfall secrets generate and cloudfall secrets input: keep the secrets a LoggingStack requires sops-encrypted under secrets/, generated or typed at a terminal with echo off; requirements show gives secrets a state and lists the missing ones (S-011)
  • deploy, rollback, restart and an artifact build hold their component's lock under tmp/locks/ on the management host until they end, passed, failed or interrupted, so a second run of the same component exits CONFLICT (component_locked) before any server is contacted, naming who holds the lock, since when, and whether that process still runs; cloudfall lock clear <component> shows a lock a killed run left, with its age, and removes it once a person types the component id at a terminal, never while its process still runs on this host (#221)
  • deploy.yml, rollback.yml and restart.yml hold the component's lock on each server, at /var/lib/cloudfall/locks/<component>.json, from before they change anything there until that server's turn ends, passed or failed, so runs from two controllers, cloudfall-engine playbook run and approved runs of those playbooks no longer race on current, the unit file or the release command's unit: a second run fails on that server, naming the action, user, controller, start time and age of the lock it found (#221)
  • The PostgreSQL backup writes globals-<timestamp>.sql from pg_dumpall --globals-only --no-role-passwords beside the per-database dumps, so a restore onto a fresh server has its roles; retention prunes it with the dumps (#225)
  • Baseline storage.pools: existing LVM volume groups that workload volumes go into; each LoggingStack volume names its pool, LV, LV type and physical volumes in requirements show, and config validate refuses a volume with no pool (S-014)
  • audit checks each required volume (volume.<name>: type, physical volumes, size, health, mount) from new volumes evidence inspect collects (S-014)
  • cloudfall logging deploy provides the stack's data volumes: a read-only report from each host, refusals decided on the controller before any host change (volume_refused), then lvcreate/mkfs for missing volumes, lvextend --resizefs for small ones, an fstab line by UUID, the mount and RequiresMountsFor drop-ins (S-014)
  • cloudfall decisions mark-interrupted <id> --confirm-dead and cloudfall operator mark-interrupted <id> --confirm-dead close a record left running by a run that died midway as the new status interrupted, once a person confirmed the run is dead; the record keeps its approval and gains interruption.confirmedBy (--by, default USER) and interruption.confirmedAt. Nothing runs on the fleet, and neither command is an MCP tool (#244)
  • AlertChannel (alert-channels/): a Telegram chat that a Baseline's hosts and a LoggingStack receiver name; its bot token is an input secret on every server that sends, set with cloudfall secrets input telegram-bot-token --owner <channel> (S-015)
  • A LoggingStack receiver may name an AlertChannel: Alertmanager delivers to it with its native telegram_configs and bot_token_file, the token delivered by logging deploy; an Alertmanager older than 0.26 is refused before its configuration is written (S-015)
  • cloudfall alerts test <server>: send one test message through the server's alert channel; audit checks each host's channel (alerting.channel: sender, token and chat id present, mdadm and smartd pointed at the sender) from new alertChannel evidence inspect collects, never the token (S-015)
  • cloudfall baseline converge: run baseline.yml with each host's alert channel; hosts whose baseline names an AlertChannel get /usr/local/sbin/cloudfall-alert, the channel's token and chat id, and mdadm and smartd pointed at the sender; a token not in the store stops it before any server (S-015)
  • A CI deploy guide (docs/ci-deploy-guide.md): one GitHub Actions workflow that renders secrets, builds the artifact with cloudfall-engine artifact build, deploys with cloudfall deploy --yes and uploads the receipts, with one SSH key and one age key per environment and required reviewers standing in for approval: manual, which deploy does not enforce; not yet run against a real server (#89)
  • An open proposal whose basis hosts have been observed again since is now reported as stale: decisions list, decisions show and cloudfall why add stale and staleHosts to each proposed decision, --stale on decisions list and why keeps only those, and decisions approve names each stale host and its newer observation time before asking for the id. Worked out on read from the observation files; the record and its schema do not change (#26)

Changed

  • Breaking: cloudfall config validate now refuses a Component with runtime.type node or pm2, or runtime.packageManager npm, pnpm or yarn, with CONFIG_INVALID and code component_runtime_unsupported naming the field: these configs validated before but could never deploy, since the deploy role runs only Python with uv. The schema keeps those values as reserved. The Render importer no longer writes a Component for a Node service; it lists the service as an unsupported gap instead (#114)
  • migrate --yes checks a deploy:<component> step's approval as deploy --yes does: for an application that declares approval: manual and no approval that counts, it pauses at that step with PARTIAL_FAILURE, context.code: deployment_approval_missing, the built release and the cloudfall release approve command, and once a person approved it, migrate --yes resumes there with the release the completed build:<component> step recorded, without building again and without needing --build again. The deploy step's detail gains approval (the record it went on), migrate gains --approvals (default decisions/releases, bound by cloudfall mcp serve) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval. rollback needs no approval: its plan gains approval, {"policy": "manual", "required": false, "reason": ...} for a manual application and {"policy": "automatic"} otherwise (#165)
  • The resource every server runs is now kind: Baseline, stored under baselines/, referenced as Server.spec.baseline and checked by baseline.schema.json (was ServerType, server-types/, spec.serverType, server-type.schema.json); cloudfall add baseline declares one and cloudfall add server --baseline names it (#198)
  • Outputs carry the new names: inventory show writes baselines and each server's baseline, config validate counts Baseline in by_kind, audit writes each server's baseline and checks baseline.id (was server_type.id; until 0.9.0 an operator proposal recorded with server_type.id verifies once baseline.id is compliant, and blocks a new proposal for the same drift), the inspect role records baseline in observed server snapshots, the rendered Ansible inventory has the host variable cloudfall_baseline, the brownfield catalog variable is cloudfall_baselines, and the error code server_type_entry_duplicate is baseline_entry_duplicate (#198)
  • Site: cloudfall.tech is the primary domain; cloudfall.dev and both www hosts redirect to it with a 301, and the PyPI homepage and the README cloudfall init writes point there (#199)
  • Contract: cloudfall lock clear <component> now also reads the component's lock on each of its servers through the new lock.yml, shows them with their ages in the same prompt, and once the component id is typed removes exactly the locks it showed; it takes --engine and --inventory-file, answers serverLocks and unreadServers (a server it could not reach), may exit ENGINE_STEP_FAILED, and is listed among the commands that change servers (#221)
  • A LoggingStack now needs a storage pool on its backend's baseline (S-014-2)
  • Site: contact addresses moved to cloudfall.tech (pilot@, conduct@); mail to cloudfall.dev still arrives (#260)
  • The logging backend and collector roles declare Debian 13 (trixie) next to Debian 12, like every other bundled role, so a trixie host built from the bundled Debian 13 baseline can carry the logging stack. Loki, Grafana and Alloy come from Grafana's distribution-independent APT repository; Prometheus comes from the host's Debian release, so a software.prometheusPackageVersion pin must name a version that release ships

Security

  • An owner role's password no longer reaches the PostgreSQL host or server: services.yml and every path that runs it compute the password's SCRAM-SHA-256 verifier on the controller (a fresh 16-byte salt, 4096 iterations, the password prepared with SASLprep as PostgreSQL does) and stage that verifier in the 0600 file instead of the password, so ALTER ROLE ... PASSWORD sends a verifier PostgreSQL stores as it is and the plaintext can't show in the server log under log_statement = 'ddl' or 'all', in a failing statement, or in pg_stat_activity; answers and receipts still name the reference, the key, and the password's SHA-256 (#140)
  • A declared config value is never run as an Ansible template: cloudfall-engine inventory render and the overlay cloudfall observe writes mark every string unsafe ({"__ansible_unsafe": ...}), so a value holding {{ ... }} reaches the unit file, the release command and the health check as written. Before, a service.command, healthCheck.command or release.command argument such as {{ lookup('pipe', '...') }} ran on the management host during cloudfall health or cloudfall deploy, and an honest one such as docker inspect --format {{.State.Health.Status}} app failed with a template syntax error. A declared value that relied on Ansible evaluating {{ ... }} is now literal, and the rendered inventory's strings read as {"__ansible_unsafe": "..."} in its JSON and in ansible-inventory --list (#174)
  • A catalog operation's inputs are never run as an Ansible template: cloudfall operations propose, cloudfall decisions approve and cloudfall agent investigate hand them to the team's playbook in --extra-vars with every string marked unsafe ({"__ansible_unsafe": ...}), so an input holding {{ ... }} reaches the playbook as written, and integers and booleans keep their types. Before, an input such as {{ lookup('pipe', '...') }} ran on the management host with the operator's rights when the playbook started, and an honest input holding {{ failed with a template syntax error. A team playbook that relied on an input being evaluated as Jinja now gets the literal text. The decision record's inputs are unchanged, and recordings made before this change replay as before (#181)

Fixed

  • cloudfall audit no longer reports drift on a server whose PostgreSQL service declares spec.postgresql.remoteAccess: firewall.allowedInbound expects one tcp/<port> from <cidr> entry per declared source and reads the ip saddr/ip6 saddr match of each accepted nftables rule (a single address printed bare by nft compares equal to its /32 or /128), and services.bind[<id>] requires a listener on the declared listenAddress as well as on the bind address, reporting loopbackOnly: false and a remoteAccess.listenAddress key for such a service; a missing listenAddress listener, any other non-loopback listener, an unrestricted rule on the port and an undeclared source are drift. Servers without remoteAccess audit exactly as before. The engine and the audit now derive the source-restricted rules from one SDK function, remote_access_rules_for_server (#143)
  • A pg_hba.conf reload that failed is no longer forgotten: services.yml leaves a marker file at /var/lib/cloudfall/postgresql/<service>.pg_hba-reload-pending when it closes remote access after a failed check or reload, and the next converge checks and reloads pg_hba.conf even though the file is unchanged, then removes the marker, so the old hostssl lines no longer stay live until a restart (#144)
  • cloudfall config validate refuses an owned database or owner named all, sameuser, samerole, samegroup or replication on a PostgreSQL service with remoteAccess, as CONFIG_INVALID with code service_remote_access_name_reserved, instead of leaving the refusal to the converge; without remoteAccess those names still validate (#144)
  • A first deploy over a hand-made systemd unit of the same name no longer loses it when the release fails its health gate: the deploy role keeps a unit without the # Managed by Cloudfall header at /etc/systemd/system/<name>.service.pre-cloudfall before installing the managed unit, and on a failed first release copies it back, restores its enabled state and starts it again when it was active; check mode reports the unit it would keep, and a hand-made unit that differs from an earlier kept copy refuses the deploy (#151)
  • The data copy preflight now names an extension that a selected table needs through an array or a domain of the extension's type, such as a citext[] column or a column of a domain over citext (chained domains included), under extensions and passes it to pg_dump --extension; before, only a direct use of the extension's type was seen, so the copy skipped the extension and the restore failed (#173)
  • cloudfall migrate --yes no longer crashes with HANDLER_CRASHED when it reaches its audit or verify-routes step on a project with no server observations: the step fails with migrate_observations_missing, naming the missing directory and cloudfall observe, and a rerun after observe resumes at that step (#183)
  • Decision records and operator proposal receipts are written through a temporary file and renamed into place, so a crash or a full disk mid-write no longer leaves a truncated record; a new record is created exclusively, so two writers of one id can no longer both succeed, and each read-modify-write of a record holds its directory's lock (#217)
  • An approval is recorded, with the new status running, before the first playbook or the operator's executor starts. A run killed midway stays running and is refused by decisions approve and operator approve with PRECONDITION (decision_run_interrupted, operator_proposal_run_interrupted) instead of being approvable and run a second time; running is added to both record schemas (#217)
  • deploy, rollback and restart contact only the component's own servers (its component_<id> inventory group, still in inventory order), and a backup contacts only the service's server, so an unreachable server the component or service is not on no longer fails them; a component with no servers in the inventory, or a service on no inventory server, now fails before any host is contacted (#220)
  • Deploying the release that is already current unpacks into a fresh releases/<release>.redeploy-<UTC time> directory instead of writing into the live one, so a failed health gate rolls back to the untouched copy; rollback to that release id takes its newest copy, and receipts still name the release id (#223)
  • A failed health gate restores the service unit the previous release ran under, not only the current symlink, then gates the restored release on its health check; a restored release that fails it fails the deploy with its own message (#223)
  • deploy.yml --check runs to its end: the dry run reports the uv release it would install and skips the digest check, the unpack and uv sync of an archive it never transferred (#223)
  • The PostgreSQL restore drill compares the row count of every table the dump holds with the restored table and fails on a difference or on a dump without a table; it counted pg_class rows before, which an empty database has too, so a restore that brought back nothing passed (#225)
  • The restore drill's scratch database keeps to PostgreSQL's 63-byte names (<database>_restore_check, the name cut to 49 characters), and cloudfall config validate and the converge refuse a declared database named as another's scratch database, as CONFIG_INVALID with code service_database_restore_check_name (#225)
  • The test suite passes on a checkout whose config/examples/tmp/ holds rendered inventory or observations (as task inventory and CI leave it): every test that copies the examples now goes through one helper, sdk/tests/examples_project.py, that leaves that folder behind, and a test refuses a direct copy (#226)
  • Docs that no longer matched the code: ARCHITECTURE.md now says a project pins cloudfall==<version>, that decision records are committed while runtime state stays under tmp/, and which Taskfile.yml tasks call Ansible directly; the AGENTS.md that cloudfall init writes names the cloudfall==<version> pin instead of a rev pin; CONTRIBUTING.md names config/ instead of a state/ directory; the CLI evaluation under evaluations/cloudfall/ uses repository-relative paths (#229)
  • An operator proposal left running no longer blocks the operator for good: once closed as interrupted it stops blocking new proposals for the same alert or drift, and the refusals of decisions approve and operator approve name the command that closes it (#244)
  • A decision record or proposal receipt write now flushes its directory after the rename, so a power loss cannot bring the old record back (#244)
  • A redeploy copy (releases/<release>.redeploy-<UTC time>) that fails its health gate is removed by the deploy's rollback once the previous copy runs again, so rollback <release> takes the newest copy that passed instead of switching to the failed one; the copy's time now has microseconds, so two redeploys in the same second get two directories (#245)
  • health contacts only the component's own servers and fails before any host when the component has no servers in the inventory, instead of reporting success with nothing probed; and deploy, rollback and restart stop at the first of the component's servers they could not reach, where before Ansible skipped the unreachable server and went on to the next one (#246)
  • The PostgreSQL restore drill counts each restored table without its inheritance children (count(*) FROM ONLY), as the dump's COPY data holds them, so a database with classic table inheritance no longer fails the drill every night after a correct restore (#247)
  • config validate refuses a storage pool device path with .., a volumeGroup of . or .., and a pool naming one device as both primary and secondary (storage_pool_same_physical_volume); before, the first two passed validation and crashed requirements show (#248)
  • baseline, bootstrap, services, data, domains, logging, time and backup stop at the first server they could not reach, as deploy, rollback and restart do since #246, where before Ansible skipped the unreachable server and changed the next one; the check lives in one shared task file, playbooks/tasks/rollout-start.yml, and inspect still goes on past a server it cannot reach, reporting it as missing (#254)
  • An operator proposal closed as interrupted now suspends autonomy for its operation kind the way a failed one does, until a human-approved run verifies, and an autonomous run closed as interrupted counts toward maxAutonomousPerHour from its interruption.confirmedAt; before, a killed unattended run left the next proposal for the same alert free to run unattended while what the first run changed was unknown (#258)
  • cloudfall lock clear <component> no longer deletes a server's lock that a run took again after it was shown: lock.yml compares the shown token and removes the lock in one command on the server, instead of reading it and deleting it in two tasks, so a lock taken since is kept and the command exits CONFLICT; and with no lock found while a server could not be reached it exits CONFLICT with component_lock_not_cleared and unreadServers, instead of answering noop as if no run held the lock (#271)
  • domains.yml now fails before it changes any server when a Domain it would render has no proxy.upstream, and names every such Domain; before, the site role's assert stopped the run only on that Domain's server, after serial: 1 had already converged the servers before it. upstream stays optional in the schema, for a Domain the fleet routes with its own proxy (#90)
  • A deploy of a component with healthCheck: {type: none} no longer fails its health gate on the missing HTTP fields and stops the release: the gate now requires the systemd unit to be active right after the restart and still active, with no automatic restart in between, 10 seconds later, so a worker that crashes or crash-loops on start still fails and rolls back (#96)

Deprecated

  • kind: ServerType, the server-types/ folder, Server.spec.serverType, the cloudfall_server_types catalog variable and a host's server_type, cloudfall add server-type and cloudfall add server --type keep working until 0.9.0; cloudfall config validate warns DEPRECATED_NAME for each file using an old name, and a server setting both serverType and baseline fails with server_baseline_conflict (#198)
  • Until 0.9.0 the old output names stay beside the new ones with the same values: the rendered Ansible inventory's host variable cloudfall_server_type, inventory show's server_types and each server's server_type, config validate's by_kind.ServerType, and audit's per-server server_type; an observed server snapshot recorded with spec.serverType is still read as spec.baseline, and one with both fails with observation_baseline_conflict (#198)