Repository navigation
cloudfall 0.8.0rc27
Pre-release
Pre-release
·
215 commits
to main
since this release
Changes since v0.7.0:
Breaking
deploy --yesandmigrate --yeson an application that declaresapproval: manualnow need a person's approval of the release: without acloudfall release approverecord that counts (the same archive SHA-256, exactly the component's declared servers, not expired),deploy --yesexits 4PRECONDITIONwithdeployment_approval_missingbefore any playbook runs, naming therelease approvecommand, and lists each record that doesn't count withdigest_mismatch,servers_changedorexpired. This hits every project that declaresmanualand deploys today, the examplecrm.yamland every Render import included. Two ways out: keepmanualand approve each release first (build it, runcloudfall release approveat a terminal, commit the record underdecisions/releases/when CI deploys, then deploy), or switch the application toapproval: automaticwhen another gate, such as GitHub's required reviewers, is the real one. Thedeployplan and result gainapproval(policy, and formanualthestatus, the counting record'spath,approverandexpires_atorapproved_at, the records that don't count and thecommandto run),deploygains--approvals(defaultdecisions/releases) and theRECORD_INVALIDexit for an approvals file that isn't a validReleaseApproval, andcloudfall mcp servebinds the approvals folder (its own--approvals) so adeploycall can't name its own; anautomaticapplication's deploy never reads the folder (#163)
Added
- A Component can declare
spec.buildTools(tool name to minimum version),spec.build(ordered steps, each aworkingDirectoryinside the packaged root, an argvcommandand an optionaltimeoutSecondsfrom 1 to 3600, default 900) andspec.artifact.include(relative paths the build produces);cloudfall config validaterefuses a step whosecommand[0]is not inbuildTools(component_build_tool_undeclared), an absolute or..path, andbuildToolsorartifactwithoutbuild. Validation only:artifact builddoes not run the steps yet. Components withoutbuildvalidate as before (#113) cloudfall-engine artifact buildruns a Component's declaredspec.buildsteps on the controller before packaging: it checks everyspec.buildToolsentry is onPATHat its minimum version before cloning (artifact_build_tool_missing,artifact_build_tool_unsupported), runs each step in the clean checkout with onlyPATH,HOME,LANG,TMPDIRandCI=truein its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its owntimeoutSeconds(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 everyspec.artifact.includepath (a gitignoredweb/dist, say), and records the steps and tool versions as the new optionalspec.buildof 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--timeoutreplaces it, and--timeout 0still disables it. A Component withoutbuildis packaged as before (#115)- The
converge_domainsMCP tool takes an optionaldomain: given,domains.ymlruns only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exitsPRECONDITION(lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now recordspreviousConfigurationSha256, the sha256 of the vhost file the run replaced, ornullwhen none was there; receipts without it still load (#116) cloudfall domains apply <domain> [--issue-certificate] [--yes]converges one Domain:domains.ymlruns on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without--yesit exits 0 with a plan.--issue-certificaterefuses a Domain withtls.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); aproxiedDomain skips the check (dnsCheck: "skipped-proxied"). With--yesit answers the receipt path under--deployments(#117)cloudfall domains observe <domain>reads one Domain on its proxy server alone, through the new read-onlydomains-observe.yml: the vhost file and its sha256, the certificate's expiry,certbot.timer, and whether the vhost still matches the last receipt (receipt: nullbefore the first). It changes nothing on the server or in the project, and a missing vhost exits 0.cloudfall mcp servelistsdomains_apply(with itsyesgate) anddomains_observeas tools (#118)- Components: a
release.command(with optionalworkingDirectoryandtimeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server ofdeployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes orcurrentmoves; it runs as the application's user with the component's env file loaded under systemd'sEnvironmentFile=rules. A non-zero exit or a timeout fails the deploy withENGINE_STEP_FAILEDbefore any server switches, and a passing run is recorded asreleaseCommand(server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119) deploywithout--yesshows the component's release command asrelease_command(its command, the working directory resolved under the new release directory,timeout_secondsand the release server), ornullfor a component without one, and says inwould_runthat it runs once on that server before any switch; therollbackplan of a component with a release command showsrelease_command_skipped: true, since a rollback never runs it (#120)- A PostgreSQL
Servicedatabase may name anownerrole and itspasswordRef(environment,path,keyin the secrets store) instead of anapplication, so a project of a server and its database alone validates;spec.postgresql.remoteAccessdeclares a listen address and the client networks allowed in.config validaterefuses an entry with both or neither ofapplicationandowner, anownerwithoutpasswordRefor apasswordRefnext toapplication, a reserved owner (service_database_owner_reserved), and aremoteAccesswith 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.ymlconverges a PostgreSQL database owned by a declared role: it creates theownerlogin role, sets its password frompasswordRefas SCRAM-SHA-256 on every converge, and gives it the database; backups, the restore drill, anddata copy(restoring as the owner, its receipt'sspec.owner) cover it like any other database. Every path that runsservices.yml(theconverge_servicesMCP tool, theservicesstep ofcloudfall migrate,operator approveandoperator run, andcloudfall-engine playbook run services.yml) reads the password from a--secrets-dirflag (defaultsecrets) 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'sowned_rolesnames the reference, the key, and the value's SHA-256;operator approverecords them asownedRolesin the proposal receipt'soutcome(an optional property) andoperator runin each executed proposal's entry. A missing secrets file or key fails withPRECONDITIONnaming the expected path and key before any playbook runs (#122)- A PostgreSQL service with
spec.postgresql.remoteAccessopens to its declared sources over TLS:services.ymlsetslisten_addresses = '127.0.0.1,<listenAddress>'andssl = onwith the Debianssl-certsnakeoil pair (restarting the cluster), and writes onehostssl <database> <owner> <cidr> scram-sha-256line per owned database and source between Cloudfall markers inpg_hba.conf, reloading only afterpg_hba_file_rulesreports no error;baseline.ymladds oneip saddr/ip6 saddr <cidr> tcp dport <port> acceptrule per source, rendered as acloudfall_firewall.allowedInboundentry with a new optionalsourceslist. RemovingremoteAccessresets the listener and removes thepg_hba.confblock and the firewall rule; databases named byapplicationstay socket-only (#123) cloudfall data copytakes a repeatable--source-schema NAME(and thedata_copyMCP tool asource_schemalist): 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--yesnames 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 ofpubliconly, so a row-count mismatch outsidepublicnow fails the copy. TheDataMigrationReceiptgainsspec.schemas(sorted) and aschemaon eachspec.tables[]entry besidetableandrows(#124)cloudfall data copy, and thedata:<database>step ofcloudfall migrate, run a preflight on the target host after the empty-target check and beforepg_dump: it reads both catalogs and refuses a copy the target can't hold, with nothing dumped, the target untouched and no receipt, exitingPRECONDITIONwith codedata_copy_preflight_refusedand four lists in the error context, each item named:missingSchemas(a named schema the source lacks),extensions(one the selected schemas need, throughpg_dependor by living in them, or every source extension butplpgsqlwithout--source-schema, that the target'spg_available_extensionslacks),roles(a role a row-level security policy on a selected table names that the target'spg_roleslacks) andauthReferences(a function or policy of the selected schemas that referencesauth.whenauthisn't copied). The role writes the findings to<service>-<database>.preflight.jsonunder--data-migrations, so the lists arrive whole. With--source-schema,pg_dumpalso gets one--extensionper extension the schemas need (pg_dump 14 or later), andpg_restorenow runs with--single-transaction, so a failed restore rolls back whole, writes no receipt, exitsENGINE_STEP_FAILED, and the next run passes the empty-target check (#125)cloudfall migratetakes a repeatable--data-schema DATABASE=NAMEbeside--data DATABASE=PATH(and themigrateMCP tool adata_schemalist): thedata:<database>step copies only the named schemas, asdata copy --source-schemadoes, and the plan names them. A--source-schemaor--data-schemaname 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-schemafor a database with no--dataexitsPRECONDITION(codedata_copy_schema_invalidormigrate_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 anupstream(address,port) or serve a component's release files (static:component,directory, optionalspaFallback).cloudfall config validaterefuses a Domain with bothproxy.upstreamandroutes(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'sproxy.server(domain_route_component_not_on_proxy), and adirectoryorspaFallbackthat is absolute, climbs out with.., or, fordirectory, names the release root. Validation only: the domains playbook doesn't render routes yet and still refuses a Domain withoutproxy.upstreambefore any change. Domains with onlyproxy.upstreamvalidate and render as before (#159) cloudfall release approve <component> --release <release>records a person's approval of one built release as aReleaseApproval(newrelease-approval.schema.json) underdecisions/releases/: the application, component, release, archive SHA-256, git commit, servers, approver,approvedAt,expiresAt(--valid-forhours, 1 to 168, default 24) andvia: terminal. It verifies the artifact first, refuses a component of anautomaticapplication withrelease_approval_not_required, and writes the record only once a person typed the release id at a terminal;--yesnever answers it, and it is no MCP tool. It deploys nothing (#160)- Components: a
healthCheckoftype: command(a required non-emptycommandargv,timeoutSeconds1 to 300 andattempts1 to 20, no other key) validates, anddeploy,restartandrollbackwithout--yesname the check and its command in their plan'swouldRun(#161) cloudfall domains applyrenders a Domain'sspec.routes: a proxy route becomes alocationthat proxies to itsupstreamwith the full request path, and a static route serves<installRoot>/current/<directory>of its component, answeringspaFallbackfor 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 ACLuser:www-data:--x, installingacl) from the application root to the install root and itsreleases/, so it reads the release files but nevershared/env/<component>.env, and a deploy orcloudfall rollbackswitches 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 neitherproxy.upstreamnorroutes. A Domain with onlyproxy.upstreamrenders a byte-identical vhost (#162)- Deploy: a component's
healthCheckoftype: commandnow gatesdeploy --yes. After the switch and the restart it runs on each server in a transient systemd unitcloudfall-health-<component>, as the application's user, in<installRoot>/current, with the service's env file andtimeoutSecondsas its runtime limit, up toattemptstimes 3 seconds apart. When every attempt fails or times out, the previous release is restored (a first release is stopped), the deploy fails withENGINE_STEP_FAILEDnaming the check and its exit code or timeout, and the release receipt is written withhealthCheckPassed: false. Receipts of a command check carryhealthCheck(command, attempts, exit code, timed out), never the command's output, which stays in the server's journal. The release receipt schema acceptshealthCheckPassed: falseonly with a failed commandhealthCheck, and every receipt written before (#164) restart,rollbackandhealthrun a component'stype: commandhealth check instead of refusing it: the same transient unit asdeploy's gate, with its user, working directory, env file, timeout, attempts and redacted output.healthreportsunhealthywhen the check exits non-zero or times out, a failed check failsrestartorrollbackwithout restoring anything, as anhttpcheck does, and none of them writes a release receipt. The check starts its unit as root, sohealthof such a component needs the inventory SSH account to become root, asrestartandrollbackalready do;httpandnonechecks are unchanged (#166)cloudfall config upgrade: rewrites a project from the deprecatedServerTypenames toBaseline(movesserver-types/tobaselines/, rewriteskindandspec.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)auditchecks the certificates a server's host requirements name (present, for the right names, more than 30 days left at the observation's time) from newcertificatesevidenceinspectcollects, and expects the logging gateway's firewall rule, so a deployed stack audits compliant (S-011)cloudfall logging deployprovides 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 declaredLoggingStackafter 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--yesit 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
remoteAccessrules and enforced bylogging.yml; a remote collector with no IP behind a firewall failsconfig validate(logging_gateway_collector_unaddressed) (S-011) LoggingStack:migration.mode: nonefor a host with no legacy agents;parallelstill requirespreserveLegacyAgents: 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 declaredLoggingStackneeds from its servers, by server (S-011)cloudfall secrets generateandcloudfall secrets input: keep the secrets aLoggingStackrequires sops-encrypted undersecrets/, generated or typed at a terminal with echo off;requirements showgives secrets a state and lists the missing ones (S-011)deploy,rollback,restartand an artifact build hold their component's lock undertmp/locks/on the management host until they end, passed, failed or interrupted, so a second run of the same component exitsCONFLICT(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.ymlandrestart.ymlhold 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 runand approved runs of those playbooks no longer race oncurrent, 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>.sqlfrompg_dumpall --globals-only --no-role-passwordsbeside the per-database dumps, so a restore onto a fresh server has its roles; retention prunes it with the dumps (#225) Baselinestorage.pools: existing LVM volume groups that workload volumes go into; eachLoggingStackvolume names its pool, LV, LV type and physical volumes inrequirements show, andconfig validaterefuses a volume with no pool (S-014)auditchecks each required volume (volume.<name>: type, physical volumes, size, health, mount) from newvolumesevidenceinspectcollects (S-014)cloudfall logging deployprovides the stack's data volumes: a read-only report from each host, refusals decided on the controller before any host change (volume_refused), thenlvcreate/mkfsfor missing volumes,lvextend --resizefsfor small ones, an fstab line by UUID, the mount andRequiresMountsFordrop-ins (S-014)cloudfall decisions mark-interrupted <id> --confirm-deadandcloudfall operator mark-interrupted <id> --confirm-deadclose a record leftrunningby a run that died midway as the new statusinterrupted, once a person confirmed the run is dead; the record keeps its approval and gainsinterruption.confirmedBy(--by, defaultUSER) andinterruption.confirmedAt. Nothing runs on the fleet, and neither command is an MCP tool (#244)AlertChannel(alert-channels/): a Telegram chat that aBaseline's hosts and aLoggingStackreceiver name; its bot token is an input secret on every server that sends, set withcloudfall secrets input telegram-bot-token --owner <channel>(S-015)- A
LoggingStackreceiver may name anAlertChannel: Alertmanager delivers to it with its nativetelegram_configsandbot_token_file, the token delivered bylogging 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;auditchecks each host's channel (alerting.channel: sender, token and chat id present, mdadm and smartd pointed at the sender) from newalertChannelevidenceinspectcollects, never the token (S-015)cloudfall baseline converge: runbaseline.ymlwith each host's alert channel; hosts whose baseline names anAlertChannelget/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 withcloudfall-engine artifact build, deploys withcloudfall deploy --yesand uploads the receipts, with one SSH key and one age key per environment and required reviewers standing in forapproval: manual, whichdeploydoes 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 showandcloudfall whyaddstaleandstaleHoststo eachproposeddecision,--staleondecisions listandwhykeeps only those, anddecisions approvenames 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 validatenow refuses a Component withruntime.typenodeorpm2, orruntime.packageManagernpm,pnpmoryarn, withCONFIG_INVALIDand codecomponent_runtime_unsupportednaming 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 --yeschecks adeploy:<component>step's approval asdeploy --yesdoes: for an application that declaresapproval: manualand no approval that counts, it pauses at that step withPARTIAL_FAILURE,context.code: deployment_approval_missing, the builtreleaseand thecloudfall release approvecommand, and once a person approved it,migrate --yesresumes there with the release the completedbuild:<component>step recorded, without building again and without needing--buildagain. The deploy step's detail gainsapproval(the record it went on),migrategains--approvals(defaultdecisions/releases, bound bycloudfall mcp serve) and theRECORD_INVALIDexit for an approvals file that isn't a validReleaseApproval.rollbackneeds no approval: its plan gainsapproval,{"policy": "manual", "required": false, "reason": ...}for amanualapplication and{"policy": "automatic"}otherwise (#165)- The resource every server runs is now
kind: Baseline, stored underbaselines/, referenced asServer.spec.baselineand checked bybaseline.schema.json(wasServerType,server-types/,spec.serverType,server-type.schema.json);cloudfall add baselinedeclares one andcloudfall add server --baselinenames it (#198) - Outputs carry the new names:
inventory showwritesbaselinesand each server'sbaseline,config validatecountsBaselineinby_kind,auditwrites each server'sbaselineand checksbaseline.id(wasserver_type.id; until 0.9.0 an operator proposal recorded withserver_type.idverifies oncebaseline.idis compliant, and blocks a new proposal for the same drift), the inspect role recordsbaselinein observed server snapshots, the rendered Ansible inventory has the host variablecloudfall_baseline, the brownfield catalog variable iscloudfall_baselines, and the error codeserver_type_entry_duplicateisbaseline_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 initwrites point there (#199) - Contract:
cloudfall lock clear <component>now also reads the component's lock on each of its servers through the newlock.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--engineand--inventory-file, answersserverLocksandunreadServers(a server it could not reach), may exitENGINE_STEP_FAILED, and is listed among the commands that change servers (#221) - A
LoggingStacknow 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.prometheusPackageVersionpin must name a version that release ships
Security
- An owner role's password no longer reaches the PostgreSQL host or server:
services.ymland 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 the0600file instead of the password, soALTER ROLE ... PASSWORDsends a verifier PostgreSQL stores as it is and the plaintext can't show in the server log underlog_statement = 'ddl'or'all', in a failing statement, or inpg_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 renderand the overlaycloudfall observewrites mark every string unsafe ({"__ansible_unsafe": ...}), so a value holding{{ ... }}reaches the unit file, the release command and the health check as written. Before, aservice.command,healthCheck.commandorrelease.commandargument such as{{ lookup('pipe', '...') }}ran on the management host duringcloudfall healthorcloudfall deploy, and an honest one such asdocker inspect --format {{.State.Health.Status}} appfailed 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 inansible-inventory --list(#174) - A catalog operation's inputs are never run as an Ansible template:
cloudfall operations propose,cloudfall decisions approveandcloudfall agent investigatehand them to the team's playbook in--extra-varswith 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'sinputsare unchanged, and recordings made before this change replay as before (#181)
Fixed
cloudfall auditno longer reports drift on a server whose PostgreSQL service declaresspec.postgresql.remoteAccess:firewall.allowedInboundexpects onetcp/<port> from <cidr>entry per declared source and reads theip saddr/ip6 saddrmatch of each accepted nftables rule (a single address printed bare by nft compares equal to its/32or/128), andservices.bind[<id>]requires a listener on the declaredlistenAddressas well as on the bind address, reportingloopbackOnly: falseand aremoteAccess.listenAddresskey for such a service; a missinglistenAddresslistener, any other non-loopback listener, an unrestricted rule on the port and an undeclared source are drift. Servers withoutremoteAccessaudit 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.confreload that failed is no longer forgotten:services.ymlleaves a marker file at/var/lib/cloudfall/postgresql/<service>.pg_hba-reload-pendingwhen it closes remote access after a failed check or reload, and the next converge checks and reloadspg_hba.confeven though the file is unchanged, then removes the marker, so the oldhostssllines no longer stay live until a restart (#144) cloudfall config validaterefuses an owned database or owner namedall,sameuser,samerole,samegrouporreplicationon a PostgreSQL service withremoteAccess, asCONFIG_INVALIDwith codeservice_remote_access_name_reserved, instead of leaving the refusal to the converge; withoutremoteAccessthose 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 Cloudfallheader at/etc/systemd/system/<name>.service.pre-cloudfallbefore 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 overcitext(chained domains included), underextensionsand passes it topg_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 --yesno longer crashes withHANDLER_CRASHEDwhen it reaches itsauditorverify-routesstep on a project with no server observations: the step fails withmigrate_observations_missing, naming the missing directory andcloudfall observe, and a rerun afterobserveresumes 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 staysrunningand is refused bydecisions approveandoperator approvewithPRECONDITION(decision_run_interrupted,operator_proposal_run_interrupted) instead of being approvable and run a second time;runningis added to both record schemas (#217) deploy,rollbackandrestartcontact only the component's own servers (itscomponent_<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
currentunpacks into a freshreleases/<release>.redeploy-<UTC time>directory instead of writing into the live one, so a failed health gate rolls back to the untouched copy;rollbackto 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
currentsymlink, 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 --checkruns to its end: the dry run reports the uv release it would install and skips the digest check, the unpack anduv syncof 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_classrows 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), andcloudfall config validateand the converge refuse a declared database named as another's scratch database, asCONFIG_INVALIDwith codeservice_database_restore_check_name(#225) - The test suite passes on a checkout whose
config/examples/tmp/holds rendered inventory or observations (astask inventoryand 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.mdnow says a project pinscloudfall==<version>, that decision records are committed while runtime state stays undertmp/, and whichTaskfile.ymltasks call Ansible directly; theAGENTS.mdthatcloudfall initwrites names thecloudfall==<version>pin instead of arevpin;CONTRIBUTING.mdnamesconfig/instead of astate/directory; the CLI evaluation underevaluations/cloudfall/uses repository-relative paths (#229) - An operator proposal left
runningno longer blocks the operator for good: once closed asinterruptedit stops blocking new proposals for the same alert or drift, and the refusals ofdecisions approveandoperator approvename 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, sorollback <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) healthcontacts 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; anddeploy,rollbackandrestartstop 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 validaterefuses a storage pool device path with.., avolumeGroupof.or.., and a pool naming one device as bothprimaryandsecondary(storage_pool_same_physical_volume); before, the first two passed validation and crashedrequirements show(#248)baseline,bootstrap,services,data,domains,logging,timeandbackupstop at the first server they could not reach, asdeploy,rollbackandrestartdo 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, andinspectstill goes on past a server it cannot reach, reporting it as missing (#254)- An operator proposal closed as
interruptednow suspends autonomy for its operation kind the way afailedone does, until a human-approved run verifies, and an autonomous run closed asinterruptedcounts towardmaxAutonomousPerHourfrom itsinterruption.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.ymlcompares 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 exitsCONFLICT; and with no lock found while a server could not be reached it exitsCONFLICTwithcomponent_lock_not_clearedandunreadServers, instead of answeringnoopas if no run held the lock (#271)domains.ymlnow fails before it changes any server when a Domain it would render has noproxy.upstream, and names every such Domain; before, the site role's assert stopped the run only on that Domain's server, afterserial: 1had already converged the servers before it.upstreamstays 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, theserver-types/folder,Server.spec.serverType, thecloudfall_server_typescatalog variable and a host'sserver_type,cloudfall add server-typeandcloudfall add server --typekeep working until 0.9.0;cloudfall config validatewarnsDEPRECATED_NAMEfor each file using an old name, and a server setting bothserverTypeandbaselinefails withserver_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'sserver_typesand each server'sserver_type,config validate'sby_kind.ServerType, andaudit's per-serverserver_type; an observed server snapshot recorded withspec.serverTypeis still read asspec.baseline, and one with both fails withobservation_baseline_conflict(#198)