Repository navigation
Releases
Releases · cloudfall-dev/cloudfall
cloudfall 0.8.0rc91
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)- A
LoggingStacknow needs a storage pool on its backend's baseline:cloudfall config validaterefuses aLoggingStackwhose backend server'sBaselinedeclares nostorage.poolswithCONFIG_INVALIDand codevolume_requirement_pool_missing, so a project whoseLoggingStackvalidated on 0.8.0rc22 stops validating. Before upgrading, declare the volume group the Loki and Prometheus volumes go into as a pool on that baseline (storage.poolswithid,volumeGroupandprimary); with more than one pool, name it on each volume inspec.backend.storage.poolandspec.metrics.backend.storagePool, or validation refuses withvolume_requirement_pool_ambiguous(S-014-2) cloudfall config validaterefuses one SSH key (same type and body, any comment) declaredactiveandrevokedin the same environment, withCONFIG_INVALIDand codessh_public_key_lifecycle_conflict, so a project that declares a key that way stops validating; before, the baseline installed it. Before upgrading, delete the revoked declaration if the key should keep access, or mark the active onerevokedif it should not (#354)- Some source URLs that
cloudfall data copyandcloudfall migrate --dataread through--dbnamebefore are now refused, because a libpq service file can't hold them as written: a#in the database name or a query parameter value, a password that ends in whitespace, and a value holding a line break. The copy stops before anything is staged, withlifecycle_execution_failedand a reason that names the URL part without quoting it. Before upgrading, percent-encode a#there as%23; a password that ends in whitespace or holds a line break can't be staged even percent-encoded, so change that password first (#355) - Over
cloudfall mcp servein a project, a confirmed call ofdeploy,rollback,restart,migrate,data_copyordomains_apply(yes: true), or ofconverge_baseline,converge_servicesorconverge_domains(confirm_destructive: true), now runs only when anOperatorPolicygrant covers it in every environment the run touches. Any other confirmed call runs nothing: it answersPRECONDITIONwitherror.context.code: operator_approval_required,context.proposal(the id of aproposedagent record it left in the proposal store,record/operator/proposals/by default),context.command(cloudfall operator approve <id>, which a person runs at a terminal) andcontext.reasons(one line per environment, naming why no grant covers it). The same call made again while that proposal isproposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as amigratewhose pending steps are builds and controller steps likettl-lower, touches no environment whose grant could cover it, so it always proposes: its record'soperation.serversandoperation.environmentsare empty (theOperatorProposalschema now accepts empty lists there) and its reason says only a person approves it. Aconverge_*call that refuses itself before any playbook, such asconverge_domainsfor an undeclared Domain, still refuses as before and writes no record. With noOperatorPolicydeclared every confirmed call proposes; to keep the one-call flow in an environment, declare anOperatorPolicyfor it whosespec.autonomy.operationsgrants those classes (deploy,rollback,restart,migrate,data-copy,domains-apply,converge-baseline,converge-services,converge-domains) and earn itsrequiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008'sdeployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan'sapproval.selfConfirmtells an agent in advance. Amigratewith no pending step left still answerscompleteand writes no record, since there is nothing to run. On the CLI, a command without--proposalsruns as before (cloudfall deploy --yesin a shell runs the deploy), while one given--proposalsand--yes(deploy,rollback,restart,data copy,domains apply,migrate) is gated like the MCP server's call: no grant, and it proposes instead of running. A repository's server lists the same tools (#476)
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)
-...
cloudfall 0.8.0rc90
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)- A
LoggingStacknow needs a storage pool on its backend's baseline:cloudfall config validaterefuses aLoggingStackwhose backend server'sBaselinedeclares nostorage.poolswithCONFIG_INVALIDand codevolume_requirement_pool_missing, so a project whoseLoggingStackvalidated on 0.8.0rc22 stops validating. Before upgrading, declare the volume group the Loki and Prometheus volumes go into as a pool on that baseline (storage.poolswithid,volumeGroupandprimary); with more than one pool, name it on each volume inspec.backend.storage.poolandspec.metrics.backend.storagePool, or validation refuses withvolume_requirement_pool_ambiguous(S-014-2) cloudfall config validaterefuses one SSH key (same type and body, any comment) declaredactiveandrevokedin the same environment, withCONFIG_INVALIDand codessh_public_key_lifecycle_conflict, so a project that declares a key that way stops validating; before, the baseline installed it. Before upgrading, delete the revoked declaration if the key should keep access, or mark the active onerevokedif it should not (#354)- Some source URLs that
cloudfall data copyandcloudfall migrate --dataread through--dbnamebefore are now refused, because a libpq service file can't hold them as written: a#in the database name or a query parameter value, a password that ends in whitespace, and a value holding a line break. The copy stops before anything is staged, withlifecycle_execution_failedand a reason that names the URL part without quoting it. Before upgrading, percent-encode a#there as%23; a password that ends in whitespace or holds a line break can't be staged even percent-encoded, so change that password first (#355) - Over
cloudfall mcp servein a project, a confirmed call ofdeploy,rollback,restart,migrate,data_copyordomains_apply(yes: true), or ofconverge_baseline,converge_servicesorconverge_domains(confirm_destructive: true), now runs only when anOperatorPolicygrant covers it in every environment the run touches. Any other confirmed call runs nothing: it answersPRECONDITIONwitherror.context.code: operator_approval_required,context.proposal(the id of aproposedagent record it left in the proposal store,record/operator/proposals/by default),context.command(cloudfall operator approve <id>, which a person runs at a terminal) andcontext.reasons(one line per environment, naming why no grant covers it). The same call made again while that proposal isproposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as amigratewhose pending steps are builds and controller steps likettl-lower, touches no environment whose grant could cover it, so it always proposes: its record'soperation.serversandoperation.environmentsare empty (theOperatorProposalschema now accepts empty lists there) and its reason says only a person approves it. Aconverge_*call that refuses itself before any playbook, such asconverge_domainsfor an undeclared Domain, still refuses as before and writes no record. With noOperatorPolicydeclared every confirmed call proposes; to keep the one-call flow in an environment, declare anOperatorPolicyfor it whosespec.autonomy.operationsgrants those classes (deploy,rollback,restart,migrate,data-copy,domains-apply,converge-baseline,converge-services,converge-domains) and earn itsrequiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008'sdeployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan'sapproval.selfConfirmtells an agent in advance. Amigratewith no pending step left still answerscompleteand writes no record, since there is nothing to run. On the CLI, a command without--proposalsruns as before (cloudfall deploy --yesin a shell runs the deploy), while one given--proposalsand--yes(deploy,rollback,restart,data copy,domains apply,migrate) is gated like the MCP server's call: no grant, and it proposes instead of running. A repository's server lists the same tools (#476)
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)
-...
cloudfall 0.8.0rc89
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)- A
LoggingStacknow needs a storage pool on its backend's baseline:cloudfall config validaterefuses aLoggingStackwhose backend server'sBaselinedeclares nostorage.poolswithCONFIG_INVALIDand codevolume_requirement_pool_missing, so a project whoseLoggingStackvalidated on 0.8.0rc22 stops validating. Before upgrading, declare the volume group the Loki and Prometheus volumes go into as a pool on that baseline (storage.poolswithid,volumeGroupandprimary); with more than one pool, name it on each volume inspec.backend.storage.poolandspec.metrics.backend.storagePool, or validation refuses withvolume_requirement_pool_ambiguous(S-014-2) cloudfall config validaterefuses one SSH key (same type and body, any comment) declaredactiveandrevokedin the same environment, withCONFIG_INVALIDand codessh_public_key_lifecycle_conflict, so a project that declares a key that way stops validating; before, the baseline installed it. Before upgrading, delete the revoked declaration if the key should keep access, or mark the active onerevokedif it should not (#354)- Some source URLs that
cloudfall data copyandcloudfall migrate --dataread through--dbnamebefore are now refused, because a libpq service file can't hold them as written: a#in the database name or a query parameter value, a password that ends in whitespace, and a value holding a line break. The copy stops before anything is staged, withlifecycle_execution_failedand a reason that names the URL part without quoting it. Before upgrading, percent-encode a#there as%23; a password that ends in whitespace or holds a line break can't be staged even percent-encoded, so change that password first (#355) - Over
cloudfall mcp servein a project, a confirmed call ofdeploy,rollback,restart,migrate,data_copyordomains_apply(yes: true), or ofconverge_baseline,converge_servicesorconverge_domains(confirm_destructive: true), now runs only when anOperatorPolicygrant covers it in every environment the run touches. Any other confirmed call runs nothing: it answersPRECONDITIONwitherror.context.code: operator_approval_required,context.proposal(the id of aproposedagent record it left in the proposal store,record/operator/proposals/by default),context.command(cloudfall operator approve <id>, which a person runs at a terminal) andcontext.reasons(one line per environment, naming why no grant covers it). The same call made again while that proposal isproposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as amigratewhose pending steps are builds and controller steps likettl-lower, touches no environment whose grant could cover it, so it always proposes: its record'soperation.serversandoperation.environmentsare empty (theOperatorProposalschema now accepts empty lists there) and its reason says only a person approves it. Aconverge_*call that refuses itself before any playbook, such asconverge_domainsfor an undeclared Domain, still refuses as before and writes no record. With noOperatorPolicydeclared every confirmed call proposes; to keep the one-call flow in an environment, declare anOperatorPolicyfor it whosespec.autonomy.operationsgrants those classes (deploy,rollback,restart,migrate,data-copy,domains-apply,converge-baseline,converge-services,converge-domains) and earn itsrequiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008'sdeployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan'sapproval.selfConfirmtells an agent in advance. Amigratewith no pending step left still answerscompleteand writes no record, since there is nothing to run. On the CLI, a command without--proposalsruns as before (cloudfall deploy --yesin a shell runs the deploy), while one given--proposalsand--yes(deploy,rollback,restart,data copy,domains apply,migrate) is gated like the MCP server's call: no grant, and it proposes instead of running. A repository's server lists the same tools (#476)
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)
-...
cloudfall 0.8.0rc88
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)- A
LoggingStacknow needs a storage pool on its backend's baseline:cloudfall config validaterefuses aLoggingStackwhose backend server'sBaselinedeclares nostorage.poolswithCONFIG_INVALIDand codevolume_requirement_pool_missing, so a project whoseLoggingStackvalidated on 0.8.0rc22 stops validating. Before upgrading, declare the volume group the Loki and Prometheus volumes go into as a pool on that baseline (storage.poolswithid,volumeGroupandprimary); with more than one pool, name it on each volume inspec.backend.storage.poolandspec.metrics.backend.storagePool, or validation refuses withvolume_requirement_pool_ambiguous(S-014-2) cloudfall config validaterefuses one SSH key (same type and body, any comment) declaredactiveandrevokedin the same environment, withCONFIG_INVALIDand codessh_public_key_lifecycle_conflict, so a project that declares a key that way stops validating; before, the baseline installed it. Before upgrading, delete the revoked declaration if the key should keep access, or mark the active onerevokedif it should not (#354)- Some source URLs that
cloudfall data copyandcloudfall migrate --dataread through--dbnamebefore are now refused, because a libpq service file can't hold them as written: a#in the database name or a query parameter value, a password that ends in whitespace, and a value holding a line break. The copy stops before anything is staged, withlifecycle_execution_failedand a reason that names the URL part without quoting it. Before upgrading, percent-encode a#there as%23; a password that ends in whitespace or holds a line break can't be staged even percent-encoded, so change that password first (#355) - Over
cloudfall mcp servein a project, a confirmed call ofdeploy,rollback,restart,migrate,data_copyordomains_apply(yes: true), or ofconverge_baseline,converge_servicesorconverge_domains(confirm_destructive: true), now runs only when anOperatorPolicygrant covers it in every environment the run touches. Any other confirmed call runs nothing: it answersPRECONDITIONwitherror.context.code: operator_approval_required,context.proposal(the id of aproposedagent record it left in the proposal store,record/operator/proposals/by default),context.command(cloudfall operator approve <id>, which a person runs at a terminal) andcontext.reasons(one line per environment, naming why no grant covers it). The same call made again while that proposal isproposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as amigratewhose pending steps are builds and controller steps likettl-lower, touches no environment whose grant could cover it, so it always proposes: its record'soperation.serversandoperation.environmentsare empty (theOperatorProposalschema now accepts empty lists there) and its reason says only a person approves it. Aconverge_*call that refuses itself before any playbook, such asconverge_domainsfor an undeclared Domain, still refuses as before and writes no record. With noOperatorPolicydeclared every confirmed call proposes; to keep the one-call flow in an environment, declare anOperatorPolicyfor it whosespec.autonomy.operationsgrants those classes (deploy,rollback,restart,migrate,data-copy,domains-apply,converge-baseline,converge-services,converge-domains) and earn itsrequiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008'sdeployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan'sapproval.selfConfirmtells an agent in advance. Amigratewith no pending step left still answerscompleteand writes no record, since there is nothing to run. On the CLI, a command without--proposalsruns as before (cloudfall deploy --yesin a shell runs the deploy), while one given--proposalsand--yes(deploy,rollback,restart,data copy,domains apply,migrate) is gated like the MCP server's call: no grant, and it proposes instead of running. A repository's server lists the same tools (#476)
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)
-...
cloudfall 0.8.0rc87
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)- A
LoggingStacknow needs a storage pool on its backend's baseline:cloudfall config validaterefuses aLoggingStackwhose backend server'sBaselinedeclares nostorage.poolswithCONFIG_INVALIDand codevolume_requirement_pool_missing, so a project whoseLoggingStackvalidated on 0.8.0rc22 stops validating. Before upgrading, declare the volume group the Loki and Prometheus volumes go into as a pool on that baseline (storage.poolswithid,volumeGroupandprimary); with more than one pool, name it on each volume inspec.backend.storage.poolandspec.metrics.backend.storagePool, or validation refuses withvolume_requirement_pool_ambiguous(S-014-2) cloudfall config validaterefuses one SSH key (same type and body, any comment) declaredactiveandrevokedin the same environment, withCONFIG_INVALIDand codessh_public_key_lifecycle_conflict, so a project that declares a key that way stops validating; before, the baseline installed it. Before upgrading, delete the revoked declaration if the key should keep access, or mark the active onerevokedif it should not (#354)- Some source URLs that
cloudfall data copyandcloudfall migrate --dataread through--dbnamebefore are now refused, because a libpq service file can't hold them as written: a#in the database name or a query parameter value, a password that ends in whitespace, and a value holding a line break. The copy stops before anything is staged, withlifecycle_execution_failedand a reason that names the URL part without quoting it. Before upgrading, percent-encode a#there as%23; a password that ends in whitespace or holds a line break can't be staged even percent-encoded, so change that password first (#355) - Over
cloudfall mcp servein a project, a confirmed call ofdeploy,rollback,restart,migrate,data_copyordomains_apply(yes: true), or ofconverge_baseline,converge_servicesorconverge_domains(confirm_destructive: true), now runs only when anOperatorPolicygrant covers it in every environment the run touches. Any other confirmed call runs nothing: it answersPRECONDITIONwitherror.context.code: operator_approval_required,context.proposal(the id of aproposedagent record it left in the proposal store,record/operator/proposals/by default),context.command(cloudfall operator approve <id>, which a person runs at a terminal) andcontext.reasons(one line per environment, naming why no grant covers it). The same call made again while that proposal isproposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as amigratewhose pending steps are builds and controller steps likettl-lower, touches no environment whose grant could cover it, so it always proposes: its record'soperation.serversandoperation.environmentsare empty (theOperatorProposalschema now accepts empty lists there) and its reason says only a person approves it. Aconverge_*call that refuses itself before any playbook, such asconverge_domainsfor an undeclared Domain, still refuses as before and writes no record. With noOperatorPolicydeclared every confirmed call proposes; to keep the one-call flow in an environment, declare anOperatorPolicyfor it whosespec.autonomy.operationsgrants those classes (deploy,rollback,restart,migrate,data-copy,domains-apply,converge-baseline,converge-services,converge-domains) and earn itsrequiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008'sdeployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan'sapproval.selfConfirmtells an agent in advance. Amigratewith no pending step left still answerscompleteand writes no record, since there is nothing to run. On the CLI, a command without--proposalsruns as before (cloudfall deploy --yesin a shell runs the deploy), while one given--proposalsand--yes(deploy,rollback,restart,data copy,domains apply,migrate) is gated like the MCP server's call: no grant, and it proposes instead of running. A repository's server lists the same tools (#476)
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)
-...
cloudfall 0.8.0rc86
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)- A
LoggingStacknow needs a storage pool on its backend's baseline:cloudfall config validaterefuses aLoggingStackwhose backend server'sBaselinedeclares nostorage.poolswithCONFIG_INVALIDand codevolume_requirement_pool_missing, so a project whoseLoggingStackvalidated on 0.8.0rc22 stops validating. Before upgrading, declare the volume group the Loki and Prometheus volumes go into as a pool on that baseline (storage.poolswithid,volumeGroupandprimary); with more than one pool, name it on each volume inspec.backend.storage.poolandspec.metrics.backend.storagePool, or validation refuses withvolume_requirement_pool_ambiguous(S-014-2) cloudfall config validaterefuses one SSH key (same type and body, any comment) declaredactiveandrevokedin the same environment, withCONFIG_INVALIDand codessh_public_key_lifecycle_conflict, so a project that declares a key that way stops validating; before, the baseline installed it. Before upgrading, delete the revoked declaration if the key should keep access, or mark the active onerevokedif it should not (#354)- Some source URLs that
cloudfall data copyandcloudfall migrate --dataread through--dbnamebefore are now refused, because a libpq service file can't hold them as written: a#in the database name or a query parameter value, a password that ends in whitespace, and a value holding a line break. The copy stops before anything is staged, withlifecycle_execution_failedand a reason that names the URL part without quoting it. Before upgrading, percent-encode a#there as%23; a password that ends in whitespace or holds a line break can't be staged even percent-encoded, so change that password first (#355) - Over
cloudfall mcp servein a project, a confirmed call ofdeploy,rollback,restart,migrate,data_copyordomains_apply(yes: true), or ofconverge_baseline,converge_servicesorconverge_domains(confirm_destructive: true), now runs only when anOperatorPolicygrant covers it in every environment the run touches. Any other confirmed call runs nothing: it answersPRECONDITIONwitherror.context.code: operator_approval_required,context.proposal(the id of aproposedagent record it left in the proposal store,record/operator/proposals/by default),context.command(cloudfall operator approve <id>, which a person runs at a terminal) andcontext.reasons(one line per environment, naming why no grant covers it). The same call made again while that proposal isproposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as amigratewhose pending steps are builds and controller steps likettl-lower, touches no environment whose grant could cover it, so it always proposes: its record'soperation.serversandoperation.environmentsare empty (theOperatorProposalschema now accepts empty lists there) and its reason says only a person approves it. Aconverge_*call that refuses itself before any playbook, such asconverge_domainsfor an undeclared Domain, still refuses as before and writes no record. With noOperatorPolicydeclared every confirmed call proposes; to keep the one-call flow in an environment, declare anOperatorPolicyfor it whosespec.autonomy.operationsgrants those classes (deploy,rollback,restart,migrate,data-copy,domains-apply,converge-baseline,converge-services,converge-domains) and earn itsrequiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008'sdeployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan'sapproval.selfConfirmtells an agent in advance. Amigratewith no pending step left still answerscompleteand writes no record, since there is nothing to run. On the CLI, a command without--proposalsruns as before (cloudfall deploy --yesin a shell runs the deploy), while one given--proposalsand--yes(deploy,rollback,restart,data copy,domains apply,migrate) is gated like the MCP server's call: no grant, and it proposes instead of running. A repository's server lists the same tools (#476)
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)
-...
cloudfall 0.8.0rc85
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)- A
LoggingStacknow needs a storage pool on its backend's baseline:cloudfall config validaterefuses aLoggingStackwhose backend server'sBaselinedeclares nostorage.poolswithCONFIG_INVALIDand codevolume_requirement_pool_missing, so a project whoseLoggingStackvalidated on 0.8.0rc22 stops validating. Before upgrading, declare the volume group the Loki and Prometheus volumes go into as a pool on that baseline (storage.poolswithid,volumeGroupandprimary); with more than one pool, name it on each volume inspec.backend.storage.poolandspec.metrics.backend.storagePool, or validation refuses withvolume_requirement_pool_ambiguous(S-014-2) cloudfall config validaterefuses one SSH key (same type and body, any comment) declaredactiveandrevokedin the same environment, withCONFIG_INVALIDand codessh_public_key_lifecycle_conflict, so a project that declares a key that way stops validating; before, the baseline installed it. Before upgrading, delete the revoked declaration if the key should keep access, or mark the active onerevokedif it should not (#354)- Some source URLs that
cloudfall data copyandcloudfall migrate --dataread through--dbnamebefore are now refused, because a libpq service file can't hold them as written: a#in the database name or a query parameter value, a password that ends in whitespace, and a value holding a line break. The copy stops before anything is staged, withlifecycle_execution_failedand a reason that names the URL part without quoting it. Before upgrading, percent-encode a#there as%23; a password that ends in whitespace or holds a line break can't be staged even percent-encoded, so change that password first (#355) - Over
cloudfall mcp servein a project, a confirmed call ofdeploy,rollback,restart,migrate,data_copyordomains_apply(yes: true), or ofconverge_baseline,converge_servicesorconverge_domains(confirm_destructive: true), now runs only when anOperatorPolicygrant covers it in every environment the run touches. Any other confirmed call runs nothing: it answersPRECONDITIONwitherror.context.code: operator_approval_required,context.proposal(the id of aproposedagent record it left in the proposal store,record/operator/proposals/by default),context.command(cloudfall operator approve <id>, which a person runs at a terminal) andcontext.reasons(one line per environment, naming why no grant covers it). The same call made again while that proposal isproposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as amigratewhose pending steps are builds and controller steps likettl-lower, touches no environment whose grant could cover it, so it always proposes: its record'soperation.serversandoperation.environmentsare empty (theOperatorProposalschema now accepts empty lists there) and its reason says only a person approves it. Aconverge_*call that refuses itself before any playbook, such asconverge_domainsfor an undeclared Domain, still refuses as before and writes no record. With noOperatorPolicydeclared every confirmed call proposes; to keep the one-call flow in an environment, declare anOperatorPolicyfor it whosespec.autonomy.operationsgrants those classes (deploy,rollback,restart,migrate,data-copy,domains-apply,converge-baseline,converge-services,converge-domains) and earn itsrequiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008'sdeployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan'sapproval.selfConfirmtells an agent in advance. Amigratewith no pending step left still answerscompleteand writes no record, since there is nothing to run. On the CLI, a command without--proposalsruns as before (cloudfall deploy --yesin a shell runs the deploy), while one given--proposalsand--yes(deploy,rollback,restart,data copy,domains apply,migrate) is gated like the MCP server's call: no grant, and it proposes instead of running. A repository's server lists the same tools (#476)
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)
-...
cloudfall 0.8.0rc84
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)- A
LoggingStacknow needs a storage pool on its backend's baseline:cloudfall config validaterefuses aLoggingStackwhose backend server'sBaselinedeclares nostorage.poolswithCONFIG_INVALIDand codevolume_requirement_pool_missing, so a project whoseLoggingStackvalidated on 0.8.0rc22 stops validating. Before upgrading, declare the volume group the Loki and Prometheus volumes go into as a pool on that baseline (storage.poolswithid,volumeGroupandprimary); with more than one pool, name it on each volume inspec.backend.storage.poolandspec.metrics.backend.storagePool, or validation refuses withvolume_requirement_pool_ambiguous(S-014-2) cloudfall config validaterefuses one SSH key (same type and body, any comment) declaredactiveandrevokedin the same environment, withCONFIG_INVALIDand codessh_public_key_lifecycle_conflict, so a project that declares a key that way stops validating; before, the baseline installed it. Before upgrading, delete the revoked declaration if the key should keep access, or mark the active onerevokedif it should not (#354)- Some source URLs that
cloudfall data copyandcloudfall migrate --dataread through--dbnamebefore are now refused, because a libpq service file can't hold them as written: a#in the database name or a query parameter value, a password that ends in whitespace, and a value holding a line break. The copy stops before anything is staged, withlifecycle_execution_failedand a reason that names the URL part without quoting it. Before upgrading, percent-encode a#there as%23; a password that ends in whitespace or holds a line break can't be staged even percent-encoded, so change that password first (#355) - Over
cloudfall mcp servein a project, a confirmed call ofdeploy,rollback,restart,migrate,data_copyordomains_apply(yes: true), or ofconverge_baseline,converge_servicesorconverge_domains(confirm_destructive: true), now runs only when anOperatorPolicygrant covers it in every environment the run touches. Any other confirmed call runs nothing: it answersPRECONDITIONwitherror.context.code: operator_approval_required,context.proposal(the id of aproposedagent record it left in the proposal store,record/operator/proposals/by default),context.command(cloudfall operator approve <id>, which a person runs at a terminal) andcontext.reasons(one line per environment, naming why no grant covers it). The same call made again while that proposal isproposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as amigratewhose pending steps are builds and controller steps likettl-lower, touches no environment whose grant could cover it, so it always proposes: its record'soperation.serversandoperation.environmentsare empty (theOperatorProposalschema now accepts empty lists there) and its reason says only a person approves it. Aconverge_*call that refuses itself before any playbook, such asconverge_domainsfor an undeclared Domain, still refuses as before and writes no record. With noOperatorPolicydeclared every confirmed call proposes; to keep the one-call flow in an environment, declare anOperatorPolicyfor it whosespec.autonomy.operationsgrants those classes (deploy,rollback,restart,migrate,data-copy,domains-apply,converge-baseline,converge-services,converge-domains) and earn itsrequiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008'sdeployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan'sapproval.selfConfirmtells an agent in advance. Amigratewith no pending step left still answerscompleteand writes no record, since there is nothing to run. On the CLI, a command without--proposalsruns as before (cloudfall deploy --yesin a shell runs the deploy), while one given--proposalsand--yes(deploy,rollback,restart,data copy,domains apply,migrate) is gated like the MCP server's call: no grant, and it proposes instead of running. A repository's server lists the same tools (#476)
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)
-...
cloudfall 0.8.0rc83
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)- A
LoggingStacknow needs a storage pool on its backend's baseline:cloudfall config validaterefuses aLoggingStackwhose backend server'sBaselinedeclares nostorage.poolswithCONFIG_INVALIDand codevolume_requirement_pool_missing, so a project whoseLoggingStackvalidated on 0.8.0rc22 stops validating. Before upgrading, declare the volume group the Loki and Prometheus volumes go into as a pool on that baseline (storage.poolswithid,volumeGroupandprimary); with more than one pool, name it on each volume inspec.backend.storage.poolandspec.metrics.backend.storagePool, or validation refuses withvolume_requirement_pool_ambiguous(S-014-2) cloudfall config validaterefuses one SSH key (same type and body, any comment) declaredactiveandrevokedin the same environment, withCONFIG_INVALIDand codessh_public_key_lifecycle_conflict, so a project that declares a key that way stops validating; before, the baseline installed it. Before upgrading, delete the revoked declaration if the key should keep access, or mark the active onerevokedif it should not (#354)- Some source URLs that
cloudfall data copyandcloudfall migrate --dataread through--dbnamebefore are now refused, because a libpq service file can't hold them as written: a#in the database name or a query parameter value, a password that ends in whitespace, and a value holding a line break. The copy stops before anything is staged, withlifecycle_execution_failedand a reason that names the URL part without quoting it. Before upgrading, percent-encode a#there as%23; a password that ends in whitespace or holds a line break can't be staged even percent-encoded, so change that password first (#355) - Over
cloudfall mcp servein a project, a confirmed call ofdeploy,rollback,restart,migrate,data_copyordomains_apply(yes: true), or ofconverge_baseline,converge_servicesorconverge_domains(confirm_destructive: true), now runs only when anOperatorPolicygrant covers it in every environment the run touches. Any other confirmed call runs nothing: it answersPRECONDITIONwitherror.context.code: operator_approval_required,context.proposal(the id of aproposedagent record it left in the proposal store,record/operator/proposals/by default),context.command(cloudfall operator approve <id>, which a person runs at a terminal) andcontext.reasons(one line per environment, naming why no grant covers it). The same call made again while that proposal isproposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as amigratewhose pending steps are builds and controller steps likettl-lower, touches no environment whose grant could cover it, so it always proposes: its record'soperation.serversandoperation.environmentsare empty (theOperatorProposalschema now accepts empty lists there) and its reason says only a person approves it. Aconverge_*call that refuses itself before any playbook, such asconverge_domainsfor an undeclared Domain, still refuses as before and writes no record. With noOperatorPolicydeclared every confirmed call proposes; to keep the one-call flow in an environment, declare anOperatorPolicyfor it whosespec.autonomy.operationsgrants those classes (deploy,rollback,restart,migrate,data-copy,domains-apply,converge-baseline,converge-services,converge-domains) and earn itsrequiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008'sdeployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan'sapproval.selfConfirmtells an agent in advance. Amigratewith no pending step left still answerscompleteand writes no record, since there is nothing to run. On the CLI, a command without--proposalsruns as before (cloudfall deploy --yesin a shell runs the deploy), while one given--proposalsand--yes(deploy,rollback,restart,data copy,domains apply,migrate) is gated like the MCP server's call: no grant, and it proposes instead of running. A repository's server lists the same tools (#476)
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)
-...
cloudfall 0.8.0rc82
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)- A
LoggingStacknow needs a storage pool on its backend's baseline:cloudfall config validaterefuses aLoggingStackwhose backend server'sBaselinedeclares nostorage.poolswithCONFIG_INVALIDand codevolume_requirement_pool_missing, so a project whoseLoggingStackvalidated on 0.8.0rc22 stops validating. Before upgrading, declare the volume group the Loki and Prometheus volumes go into as a pool on that baseline (storage.poolswithid,volumeGroupandprimary); with more than one pool, name it on each volume inspec.backend.storage.poolandspec.metrics.backend.storagePool, or validation refuses withvolume_requirement_pool_ambiguous(S-014-2) cloudfall config validaterefuses one SSH key (same type and body, any comment) declaredactiveandrevokedin the same environment, withCONFIG_INVALIDand codessh_public_key_lifecycle_conflict, so a project that declares a key that way stops validating; before, the baseline installed it. Before upgrading, delete the revoked declaration if the key should keep access, or mark the active onerevokedif it should not (#354)- Some source URLs that
cloudfall data copyandcloudfall migrate --dataread through--dbnamebefore are now refused, because a libpq service file can't hold them as written: a#in the database name or a query parameter value, a password that ends in whitespace, and a value holding a line break. The copy stops before anything is staged, withlifecycle_execution_failedand a reason that names the URL part without quoting it. Before upgrading, percent-encode a#there as%23; a password that ends in whitespace or holds a line break can't be staged even percent-encoded, so change that password first (#355) - Over
cloudfall mcp servein a project, a confirmed call ofdeploy,rollback,restart,migrate,data_copyordomains_apply(yes: true), or ofconverge_baseline,converge_servicesorconverge_domains(confirm_destructive: true), now runs only when anOperatorPolicygrant covers it in every environment the run touches. Any other confirmed call runs nothing: it answersPRECONDITIONwitherror.context.code: operator_approval_required,context.proposal(the id of aproposedagent record it left in the proposal store,record/operator/proposals/by default),context.command(cloudfall operator approve <id>, which a person runs at a terminal) andcontext.reasons(one line per environment, naming why no grant covers it). The same call made again while that proposal isproposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as amigratewhose pending steps are builds and controller steps likettl-lower, touches no environment whose grant could cover it, so it always proposes: its record'soperation.serversandoperation.environmentsare empty (theOperatorProposalschema now accepts empty lists there) and its reason says only a person approves it. Aconverge_*call that refuses itself before any playbook, such asconverge_domainsfor an undeclared Domain, still refuses as before and writes no record. With noOperatorPolicydeclared every confirmed call proposes; to keep the one-call flow in an environment, declare anOperatorPolicyfor it whosespec.autonomy.operationsgrants those classes (deploy,rollback,restart,migrate,data-copy,domains-apply,converge-baseline,converge-services,converge-domains) and earn itsrequiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008'sdeployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan'sapproval.selfConfirmtells an agent in advance. Amigratewith no pending step left still answerscompleteand writes no record, since there is nothing to run. On the CLI, a command without--proposalsruns as before (cloudfall deploy --yesin a shell runs the deploy), while one given--proposalsand--yes(deploy,rollback,restart,data copy,domains apply,migrate) is gated like the MCP server's call: no grant, and it proposes instead of running. A repository's server lists the same tools (#476)
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)
-...