Skip to content

Releases

cloudfall 0.8.0rc91

cloudfall 0.8.0rc91 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 22 Nov 05:19

Changes since v0.7.0:

Breaking

  • deploy --yes and migrate --yes on an application that declares approval: manual now need a person's approval of the release: without a cloudfall release approve record that counts (the same archive SHA-256, exactly the component's declared servers, not expired), deploy --yes exits 4 PRECONDITION with deployment_approval_missing before any playbook runs, naming the release approve command, and lists each record that doesn't count with digest_mismatch, servers_changed or expired. This hits every project that declares manual and deploys today, the example crm.yaml and every Render import included. Two ways out: keep manual and approve each release first (build it, run cloudfall release approve at a terminal, commit the record under decisions/releases/ when CI deploys, then deploy), or switch the application to approval: automatic when another gate, such as GitHub's required reviewers, is the real one. The deploy plan and result gain approval (policy, and for manual the status, the counting record's path, approver and expires_at or approved_at, the records that don't count and the command to run), deploy gains --approvals (default decisions/releases) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval, and cloudfall mcp serve binds the approvals folder (its own --approvals) so a deploy call can't name its own; an automatic application's deploy never reads the folder (#163)
  • A LoggingStack now needs a storage pool on its backend's baseline: cloudfall config validate refuses a LoggingStack whose backend server's Baseline declares no storage.pools with CONFIG_INVALID and code volume_requirement_pool_missing, so a project whose LoggingStack validated 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.pools with id, volumeGroup and primary); with more than one pool, name it on each volume in spec.backend.storage.pool and spec.metrics.backend.storagePool, or validation refuses with volume_requirement_pool_ambiguous (S-014-2)
  • cloudfall config validate refuses one SSH key (same type and body, any comment) declared active and revoked in the same environment, with CONFIG_INVALID and code ssh_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 one revoked if it should not (#354)
  • Some source URLs that cloudfall data copy and cloudfall migrate --data read through --dbname before 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, with lifecycle_execution_failed and 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 serve in a project, a confirmed call of deploy, rollback, restart, migrate, data_copy or domains_apply (yes: true), or of converge_baseline, converge_services or converge_domains (confirm_destructive: true), now runs only when an OperatorPolicy grant covers it in every environment the run touches. Any other confirmed call runs nothing: it answers PRECONDITION with error.context.code: operator_approval_required, context.proposal (the id of a proposed agent 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) and context.reasons (one line per environment, naming why no grant covers it). The same call made again while that proposal is proposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as a migrate whose pending steps are builds and controller steps like ttl-lower, touches no environment whose grant could cover it, so it always proposes: its record's operation.servers and operation.environments are empty (the OperatorProposal schema now accepts empty lists there) and its reason says only a person approves it. A converge_* call that refuses itself before any playbook, such as converge_domains for an undeclared Domain, still refuses as before and writes no record. With no OperatorPolicy declared every confirmed call proposes; to keep the one-call flow in an environment, declare an OperatorPolicy for it whose spec.autonomy.operations grants those classes (deploy, rollback, restart, migrate, data-copy, domains-apply, converge-baseline, converge-services, converge-domains) and earn its requiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008's deployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan's approval.selfConfirm tells an agent in advance. A migrate with no pending step left still answers complete and writes no record, since there is nothing to run. On the CLI, a command without --proposals runs as before (cloudfall deploy --yes in a shell runs the deploy), while one given --proposals and --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 a workingDirectory inside the packaged root, an argv command and an optional timeoutSeconds from 1 to 3600, default 900) and spec.artifact.include (relative paths the build produces); cloudfall config validate refuses a step whose command[0] is not in buildTools (component_build_tool_undeclared), an absolute or .. path, and buildTools or artifact without build. Validation only: artifact build does not run the steps yet. Components without build validate as before (#113)
  • cloudfall-engine artifact build runs a Component's declared spec.build steps on the controller before packaging: it checks every spec.buildTools entry is on PATH at its minimum version before cloning (artifact_build_tool_missing, artifact_build_tool_unsupported), runs each step in the clean checkout with only PATH, HOME, LANG, TMPDIR and CI=true in its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its own timeoutSeconds (artifact_build_step_failed), a missing include path (artifact_include_missing), an include path that leads out of the checkout through a symlink (artifact_include_outside_checkout) or a tracked file a step deleted (artifact_tracked_file_missing), packages the tracked files plus every spec.artifact.include path (a gitignored web/dist, say), and records the steps and tool versions as the new optional spec.build of the Artifact metadata. The command's time limit is now the clone time (1800 seconds) plus every declared step timeout, on the CLI and the SDK/MCP path alike; an explicit --timeout replaces it, and --timeout 0 still disables it. A Component without build is packaged as before (#115)
  • The converge_domains MCP tool takes an optional domain: given, domains.yml runs only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exits PRECONDITION (lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now records previousConfigurationSha256, the sha256 of the vhost file the run replaced, or null when none was there; receipts without it still load (#116)
  • cloudfall domains apply <domain> [--issue-certificate] [--yes] converges one Domain: domains.yml runs on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without --yes it exits 0 with a plan. --issue-certificate refuses a Domain with tls.mode: disabled, and first checks on the controller that the primary name and every alias resolve to the proxy server (PRECONDITION, domains_dns_unverified, naming each failing name); a proxied Domain skips the check (dnsCheck: "skipped-proxied"). With --yes it answers the receipt path under --deployments (#117)
  • cloudfall domains observe <domain> reads one Domain on its proxy server alone, through the new read-only domains-observe.yml: the vhost file and its sha256, the certificate's expiry, certbot.timer, and whether the vhost still matches the last receipt (receipt: null before the first). It changes nothing on the server or in the project, and a missing vhost exits 0. cloudfall mcp serve lists domains_apply (with its yes gate) and domains_observe as tools (#118)
  • Components: a release.command (with optional workingDirectory and timeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server of deployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes or current moves; it runs as the application's user with the component's env file loaded under systemd's EnvironmentFile= rules. A non-zero exit or a timeout fails the deploy with ENGINE_STEP_FAILED before any server switches, and a passing run is recorded as releaseCommand (server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119)
    -...
Read more

cloudfall 0.8.0rc90

cloudfall 0.8.0rc90 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 21 Nov 19:58

Changes since v0.7.0:

Breaking

  • deploy --yes and migrate --yes on an application that declares approval: manual now need a person's approval of the release: without a cloudfall release approve record that counts (the same archive SHA-256, exactly the component's declared servers, not expired), deploy --yes exits 4 PRECONDITION with deployment_approval_missing before any playbook runs, naming the release approve command, and lists each record that doesn't count with digest_mismatch, servers_changed or expired. This hits every project that declares manual and deploys today, the example crm.yaml and every Render import included. Two ways out: keep manual and approve each release first (build it, run cloudfall release approve at a terminal, commit the record under decisions/releases/ when CI deploys, then deploy), or switch the application to approval: automatic when another gate, such as GitHub's required reviewers, is the real one. The deploy plan and result gain approval (policy, and for manual the status, the counting record's path, approver and expires_at or approved_at, the records that don't count and the command to run), deploy gains --approvals (default decisions/releases) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval, and cloudfall mcp serve binds the approvals folder (its own --approvals) so a deploy call can't name its own; an automatic application's deploy never reads the folder (#163)
  • A LoggingStack now needs a storage pool on its backend's baseline: cloudfall config validate refuses a LoggingStack whose backend server's Baseline declares no storage.pools with CONFIG_INVALID and code volume_requirement_pool_missing, so a project whose LoggingStack validated 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.pools with id, volumeGroup and primary); with more than one pool, name it on each volume in spec.backend.storage.pool and spec.metrics.backend.storagePool, or validation refuses with volume_requirement_pool_ambiguous (S-014-2)
  • cloudfall config validate refuses one SSH key (same type and body, any comment) declared active and revoked in the same environment, with CONFIG_INVALID and code ssh_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 one revoked if it should not (#354)
  • Some source URLs that cloudfall data copy and cloudfall migrate --data read through --dbname before 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, with lifecycle_execution_failed and 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 serve in a project, a confirmed call of deploy, rollback, restart, migrate, data_copy or domains_apply (yes: true), or of converge_baseline, converge_services or converge_domains (confirm_destructive: true), now runs only when an OperatorPolicy grant covers it in every environment the run touches. Any other confirmed call runs nothing: it answers PRECONDITION with error.context.code: operator_approval_required, context.proposal (the id of a proposed agent 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) and context.reasons (one line per environment, naming why no grant covers it). The same call made again while that proposal is proposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as a migrate whose pending steps are builds and controller steps like ttl-lower, touches no environment whose grant could cover it, so it always proposes: its record's operation.servers and operation.environments are empty (the OperatorProposal schema now accepts empty lists there) and its reason says only a person approves it. A converge_* call that refuses itself before any playbook, such as converge_domains for an undeclared Domain, still refuses as before and writes no record. With no OperatorPolicy declared every confirmed call proposes; to keep the one-call flow in an environment, declare an OperatorPolicy for it whose spec.autonomy.operations grants those classes (deploy, rollback, restart, migrate, data-copy, domains-apply, converge-baseline, converge-services, converge-domains) and earn its requiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008's deployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan's approval.selfConfirm tells an agent in advance. A migrate with no pending step left still answers complete and writes no record, since there is nothing to run. On the CLI, a command without --proposals runs as before (cloudfall deploy --yes in a shell runs the deploy), while one given --proposals and --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 a workingDirectory inside the packaged root, an argv command and an optional timeoutSeconds from 1 to 3600, default 900) and spec.artifact.include (relative paths the build produces); cloudfall config validate refuses a step whose command[0] is not in buildTools (component_build_tool_undeclared), an absolute or .. path, and buildTools or artifact without build. Validation only: artifact build does not run the steps yet. Components without build validate as before (#113)
  • cloudfall-engine artifact build runs a Component's declared spec.build steps on the controller before packaging: it checks every spec.buildTools entry is on PATH at its minimum version before cloning (artifact_build_tool_missing, artifact_build_tool_unsupported), runs each step in the clean checkout with only PATH, HOME, LANG, TMPDIR and CI=true in its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its own timeoutSeconds (artifact_build_step_failed), a missing include path (artifact_include_missing), an include path that leads out of the checkout through a symlink (artifact_include_outside_checkout) or a tracked file a step deleted (artifact_tracked_file_missing), packages the tracked files plus every spec.artifact.include path (a gitignored web/dist, say), and records the steps and tool versions as the new optional spec.build of the Artifact metadata. The command's time limit is now the clone time (1800 seconds) plus every declared step timeout, on the CLI and the SDK/MCP path alike; an explicit --timeout replaces it, and --timeout 0 still disables it. A Component without build is packaged as before (#115)
  • The converge_domains MCP tool takes an optional domain: given, domains.yml runs only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exits PRECONDITION (lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now records previousConfigurationSha256, the sha256 of the vhost file the run replaced, or null when none was there; receipts without it still load (#116)
  • cloudfall domains apply <domain> [--issue-certificate] [--yes] converges one Domain: domains.yml runs on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without --yes it exits 0 with a plan. --issue-certificate refuses a Domain with tls.mode: disabled, and first checks on the controller that the primary name and every alias resolve to the proxy server (PRECONDITION, domains_dns_unverified, naming each failing name); a proxied Domain skips the check (dnsCheck: "skipped-proxied"). With --yes it answers the receipt path under --deployments (#117)
  • cloudfall domains observe <domain> reads one Domain on its proxy server alone, through the new read-only domains-observe.yml: the vhost file and its sha256, the certificate's expiry, certbot.timer, and whether the vhost still matches the last receipt (receipt: null before the first). It changes nothing on the server or in the project, and a missing vhost exits 0. cloudfall mcp serve lists domains_apply (with its yes gate) and domains_observe as tools (#118)
  • Components: a release.command (with optional workingDirectory and timeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server of deployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes or current moves; it runs as the application's user with the component's env file loaded under systemd's EnvironmentFile= rules. A non-zero exit or a timeout fails the deploy with ENGINE_STEP_FAILED before any server switches, and a passing run is recorded as releaseCommand (server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119)
    -...
Read more

cloudfall 0.8.0rc89

cloudfall 0.8.0rc89 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 21 Nov 18:58

Changes since v0.7.0:

Breaking

  • deploy --yes and migrate --yes on an application that declares approval: manual now need a person's approval of the release: without a cloudfall release approve record that counts (the same archive SHA-256, exactly the component's declared servers, not expired), deploy --yes exits 4 PRECONDITION with deployment_approval_missing before any playbook runs, naming the release approve command, and lists each record that doesn't count with digest_mismatch, servers_changed or expired. This hits every project that declares manual and deploys today, the example crm.yaml and every Render import included. Two ways out: keep manual and approve each release first (build it, run cloudfall release approve at a terminal, commit the record under decisions/releases/ when CI deploys, then deploy), or switch the application to approval: automatic when another gate, such as GitHub's required reviewers, is the real one. The deploy plan and result gain approval (policy, and for manual the status, the counting record's path, approver and expires_at or approved_at, the records that don't count and the command to run), deploy gains --approvals (default decisions/releases) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval, and cloudfall mcp serve binds the approvals folder (its own --approvals) so a deploy call can't name its own; an automatic application's deploy never reads the folder (#163)
  • A LoggingStack now needs a storage pool on its backend's baseline: cloudfall config validate refuses a LoggingStack whose backend server's Baseline declares no storage.pools with CONFIG_INVALID and code volume_requirement_pool_missing, so a project whose LoggingStack validated 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.pools with id, volumeGroup and primary); with more than one pool, name it on each volume in spec.backend.storage.pool and spec.metrics.backend.storagePool, or validation refuses with volume_requirement_pool_ambiguous (S-014-2)
  • cloudfall config validate refuses one SSH key (same type and body, any comment) declared active and revoked in the same environment, with CONFIG_INVALID and code ssh_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 one revoked if it should not (#354)
  • Some source URLs that cloudfall data copy and cloudfall migrate --data read through --dbname before 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, with lifecycle_execution_failed and 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 serve in a project, a confirmed call of deploy, rollback, restart, migrate, data_copy or domains_apply (yes: true), or of converge_baseline, converge_services or converge_domains (confirm_destructive: true), now runs only when an OperatorPolicy grant covers it in every environment the run touches. Any other confirmed call runs nothing: it answers PRECONDITION with error.context.code: operator_approval_required, context.proposal (the id of a proposed agent 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) and context.reasons (one line per environment, naming why no grant covers it). The same call made again while that proposal is proposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as a migrate whose pending steps are builds and controller steps like ttl-lower, touches no environment whose grant could cover it, so it always proposes: its record's operation.servers and operation.environments are empty (the OperatorProposal schema now accepts empty lists there) and its reason says only a person approves it. A converge_* call that refuses itself before any playbook, such as converge_domains for an undeclared Domain, still refuses as before and writes no record. With no OperatorPolicy declared every confirmed call proposes; to keep the one-call flow in an environment, declare an OperatorPolicy for it whose spec.autonomy.operations grants those classes (deploy, rollback, restart, migrate, data-copy, domains-apply, converge-baseline, converge-services, converge-domains) and earn its requiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008's deployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan's approval.selfConfirm tells an agent in advance. A migrate with no pending step left still answers complete and writes no record, since there is nothing to run. On the CLI, a command without --proposals runs as before (cloudfall deploy --yes in a shell runs the deploy), while one given --proposals and --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 a workingDirectory inside the packaged root, an argv command and an optional timeoutSeconds from 1 to 3600, default 900) and spec.artifact.include (relative paths the build produces); cloudfall config validate refuses a step whose command[0] is not in buildTools (component_build_tool_undeclared), an absolute or .. path, and buildTools or artifact without build. Validation only: artifact build does not run the steps yet. Components without build validate as before (#113)
  • cloudfall-engine artifact build runs a Component's declared spec.build steps on the controller before packaging: it checks every spec.buildTools entry is on PATH at its minimum version before cloning (artifact_build_tool_missing, artifact_build_tool_unsupported), runs each step in the clean checkout with only PATH, HOME, LANG, TMPDIR and CI=true in its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its own timeoutSeconds (artifact_build_step_failed), a missing include path (artifact_include_missing), an include path that leads out of the checkout through a symlink (artifact_include_outside_checkout) or a tracked file a step deleted (artifact_tracked_file_missing), packages the tracked files plus every spec.artifact.include path (a gitignored web/dist, say), and records the steps and tool versions as the new optional spec.build of the Artifact metadata. The command's time limit is now the clone time (1800 seconds) plus every declared step timeout, on the CLI and the SDK/MCP path alike; an explicit --timeout replaces it, and --timeout 0 still disables it. A Component without build is packaged as before (#115)
  • The converge_domains MCP tool takes an optional domain: given, domains.yml runs only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exits PRECONDITION (lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now records previousConfigurationSha256, the sha256 of the vhost file the run replaced, or null when none was there; receipts without it still load (#116)
  • cloudfall domains apply <domain> [--issue-certificate] [--yes] converges one Domain: domains.yml runs on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without --yes it exits 0 with a plan. --issue-certificate refuses a Domain with tls.mode: disabled, and first checks on the controller that the primary name and every alias resolve to the proxy server (PRECONDITION, domains_dns_unverified, naming each failing name); a proxied Domain skips the check (dnsCheck: "skipped-proxied"). With --yes it answers the receipt path under --deployments (#117)
  • cloudfall domains observe <domain> reads one Domain on its proxy server alone, through the new read-only domains-observe.yml: the vhost file and its sha256, the certificate's expiry, certbot.timer, and whether the vhost still matches the last receipt (receipt: null before the first). It changes nothing on the server or in the project, and a missing vhost exits 0. cloudfall mcp serve lists domains_apply (with its yes gate) and domains_observe as tools (#118)
  • Components: a release.command (with optional workingDirectory and timeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server of deployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes or current moves; it runs as the application's user with the component's env file loaded under systemd's EnvironmentFile= rules. A non-zero exit or a timeout fails the deploy with ENGINE_STEP_FAILED before any server switches, and a passing run is recorded as releaseCommand (server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119)
    -...
Read more

cloudfall 0.8.0rc88

cloudfall 0.8.0rc88 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 21 Nov 17:48

Changes since v0.7.0:

Breaking

  • deploy --yes and migrate --yes on an application that declares approval: manual now need a person's approval of the release: without a cloudfall release approve record that counts (the same archive SHA-256, exactly the component's declared servers, not expired), deploy --yes exits 4 PRECONDITION with deployment_approval_missing before any playbook runs, naming the release approve command, and lists each record that doesn't count with digest_mismatch, servers_changed or expired. This hits every project that declares manual and deploys today, the example crm.yaml and every Render import included. Two ways out: keep manual and approve each release first (build it, run cloudfall release approve at a terminal, commit the record under decisions/releases/ when CI deploys, then deploy), or switch the application to approval: automatic when another gate, such as GitHub's required reviewers, is the real one. The deploy plan and result gain approval (policy, and for manual the status, the counting record's path, approver and expires_at or approved_at, the records that don't count and the command to run), deploy gains --approvals (default decisions/releases) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval, and cloudfall mcp serve binds the approvals folder (its own --approvals) so a deploy call can't name its own; an automatic application's deploy never reads the folder (#163)
  • A LoggingStack now needs a storage pool on its backend's baseline: cloudfall config validate refuses a LoggingStack whose backend server's Baseline declares no storage.pools with CONFIG_INVALID and code volume_requirement_pool_missing, so a project whose LoggingStack validated 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.pools with id, volumeGroup and primary); with more than one pool, name it on each volume in spec.backend.storage.pool and spec.metrics.backend.storagePool, or validation refuses with volume_requirement_pool_ambiguous (S-014-2)
  • cloudfall config validate refuses one SSH key (same type and body, any comment) declared active and revoked in the same environment, with CONFIG_INVALID and code ssh_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 one revoked if it should not (#354)
  • Some source URLs that cloudfall data copy and cloudfall migrate --data read through --dbname before 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, with lifecycle_execution_failed and 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 serve in a project, a confirmed call of deploy, rollback, restart, migrate, data_copy or domains_apply (yes: true), or of converge_baseline, converge_services or converge_domains (confirm_destructive: true), now runs only when an OperatorPolicy grant covers it in every environment the run touches. Any other confirmed call runs nothing: it answers PRECONDITION with error.context.code: operator_approval_required, context.proposal (the id of a proposed agent 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) and context.reasons (one line per environment, naming why no grant covers it). The same call made again while that proposal is proposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as a migrate whose pending steps are builds and controller steps like ttl-lower, touches no environment whose grant could cover it, so it always proposes: its record's operation.servers and operation.environments are empty (the OperatorProposal schema now accepts empty lists there) and its reason says only a person approves it. A converge_* call that refuses itself before any playbook, such as converge_domains for an undeclared Domain, still refuses as before and writes no record. With no OperatorPolicy declared every confirmed call proposes; to keep the one-call flow in an environment, declare an OperatorPolicy for it whose spec.autonomy.operations grants those classes (deploy, rollback, restart, migrate, data-copy, domains-apply, converge-baseline, converge-services, converge-domains) and earn its requiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008's deployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan's approval.selfConfirm tells an agent in advance. A migrate with no pending step left still answers complete and writes no record, since there is nothing to run. On the CLI, a command without --proposals runs as before (cloudfall deploy --yes in a shell runs the deploy), while one given --proposals and --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 a workingDirectory inside the packaged root, an argv command and an optional timeoutSeconds from 1 to 3600, default 900) and spec.artifact.include (relative paths the build produces); cloudfall config validate refuses a step whose command[0] is not in buildTools (component_build_tool_undeclared), an absolute or .. path, and buildTools or artifact without build. Validation only: artifact build does not run the steps yet. Components without build validate as before (#113)
  • cloudfall-engine artifact build runs a Component's declared spec.build steps on the controller before packaging: it checks every spec.buildTools entry is on PATH at its minimum version before cloning (artifact_build_tool_missing, artifact_build_tool_unsupported), runs each step in the clean checkout with only PATH, HOME, LANG, TMPDIR and CI=true in its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its own timeoutSeconds (artifact_build_step_failed), a missing include path (artifact_include_missing), an include path that leads out of the checkout through a symlink (artifact_include_outside_checkout) or a tracked file a step deleted (artifact_tracked_file_missing), packages the tracked files plus every spec.artifact.include path (a gitignored web/dist, say), and records the steps and tool versions as the new optional spec.build of the Artifact metadata. The command's time limit is now the clone time (1800 seconds) plus every declared step timeout, on the CLI and the SDK/MCP path alike; an explicit --timeout replaces it, and --timeout 0 still disables it. A Component without build is packaged as before (#115)
  • The converge_domains MCP tool takes an optional domain: given, domains.yml runs only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exits PRECONDITION (lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now records previousConfigurationSha256, the sha256 of the vhost file the run replaced, or null when none was there; receipts without it still load (#116)
  • cloudfall domains apply <domain> [--issue-certificate] [--yes] converges one Domain: domains.yml runs on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without --yes it exits 0 with a plan. --issue-certificate refuses a Domain with tls.mode: disabled, and first checks on the controller that the primary name and every alias resolve to the proxy server (PRECONDITION, domains_dns_unverified, naming each failing name); a proxied Domain skips the check (dnsCheck: "skipped-proxied"). With --yes it answers the receipt path under --deployments (#117)
  • cloudfall domains observe <domain> reads one Domain on its proxy server alone, through the new read-only domains-observe.yml: the vhost file and its sha256, the certificate's expiry, certbot.timer, and whether the vhost still matches the last receipt (receipt: null before the first). It changes nothing on the server or in the project, and a missing vhost exits 0. cloudfall mcp serve lists domains_apply (with its yes gate) and domains_observe as tools (#118)
  • Components: a release.command (with optional workingDirectory and timeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server of deployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes or current moves; it runs as the application's user with the component's env file loaded under systemd's EnvironmentFile= rules. A non-zero exit or a timeout fails the deploy with ENGINE_STEP_FAILED before any server switches, and a passing run is recorded as releaseCommand (server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119)
    -...
Read more

cloudfall 0.8.0rc87

cloudfall 0.8.0rc87 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 21 Nov 14:47

Changes since v0.7.0:

Breaking

  • deploy --yes and migrate --yes on an application that declares approval: manual now need a person's approval of the release: without a cloudfall release approve record that counts (the same archive SHA-256, exactly the component's declared servers, not expired), deploy --yes exits 4 PRECONDITION with deployment_approval_missing before any playbook runs, naming the release approve command, and lists each record that doesn't count with digest_mismatch, servers_changed or expired. This hits every project that declares manual and deploys today, the example crm.yaml and every Render import included. Two ways out: keep manual and approve each release first (build it, run cloudfall release approve at a terminal, commit the record under decisions/releases/ when CI deploys, then deploy), or switch the application to approval: automatic when another gate, such as GitHub's required reviewers, is the real one. The deploy plan and result gain approval (policy, and for manual the status, the counting record's path, approver and expires_at or approved_at, the records that don't count and the command to run), deploy gains --approvals (default decisions/releases) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval, and cloudfall mcp serve binds the approvals folder (its own --approvals) so a deploy call can't name its own; an automatic application's deploy never reads the folder (#163)
  • A LoggingStack now needs a storage pool on its backend's baseline: cloudfall config validate refuses a LoggingStack whose backend server's Baseline declares no storage.pools with CONFIG_INVALID and code volume_requirement_pool_missing, so a project whose LoggingStack validated 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.pools with id, volumeGroup and primary); with more than one pool, name it on each volume in spec.backend.storage.pool and spec.metrics.backend.storagePool, or validation refuses with volume_requirement_pool_ambiguous (S-014-2)
  • cloudfall config validate refuses one SSH key (same type and body, any comment) declared active and revoked in the same environment, with CONFIG_INVALID and code ssh_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 one revoked if it should not (#354)
  • Some source URLs that cloudfall data copy and cloudfall migrate --data read through --dbname before 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, with lifecycle_execution_failed and 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 serve in a project, a confirmed call of deploy, rollback, restart, migrate, data_copy or domains_apply (yes: true), or of converge_baseline, converge_services or converge_domains (confirm_destructive: true), now runs only when an OperatorPolicy grant covers it in every environment the run touches. Any other confirmed call runs nothing: it answers PRECONDITION with error.context.code: operator_approval_required, context.proposal (the id of a proposed agent 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) and context.reasons (one line per environment, naming why no grant covers it). The same call made again while that proposal is proposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as a migrate whose pending steps are builds and controller steps like ttl-lower, touches no environment whose grant could cover it, so it always proposes: its record's operation.servers and operation.environments are empty (the OperatorProposal schema now accepts empty lists there) and its reason says only a person approves it. A converge_* call that refuses itself before any playbook, such as converge_domains for an undeclared Domain, still refuses as before and writes no record. With no OperatorPolicy declared every confirmed call proposes; to keep the one-call flow in an environment, declare an OperatorPolicy for it whose spec.autonomy.operations grants those classes (deploy, rollback, restart, migrate, data-copy, domains-apply, converge-baseline, converge-services, converge-domains) and earn its requiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008's deployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan's approval.selfConfirm tells an agent in advance. A migrate with no pending step left still answers complete and writes no record, since there is nothing to run. On the CLI, a command without --proposals runs as before (cloudfall deploy --yes in a shell runs the deploy), while one given --proposals and --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 a workingDirectory inside the packaged root, an argv command and an optional timeoutSeconds from 1 to 3600, default 900) and spec.artifact.include (relative paths the build produces); cloudfall config validate refuses a step whose command[0] is not in buildTools (component_build_tool_undeclared), an absolute or .. path, and buildTools or artifact without build. Validation only: artifact build does not run the steps yet. Components without build validate as before (#113)
  • cloudfall-engine artifact build runs a Component's declared spec.build steps on the controller before packaging: it checks every spec.buildTools entry is on PATH at its minimum version before cloning (artifact_build_tool_missing, artifact_build_tool_unsupported), runs each step in the clean checkout with only PATH, HOME, LANG, TMPDIR and CI=true in its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its own timeoutSeconds (artifact_build_step_failed), a missing include path (artifact_include_missing), an include path that leads out of the checkout through a symlink (artifact_include_outside_checkout) or a tracked file a step deleted (artifact_tracked_file_missing), packages the tracked files plus every spec.artifact.include path (a gitignored web/dist, say), and records the steps and tool versions as the new optional spec.build of the Artifact metadata. The command's time limit is now the clone time (1800 seconds) plus every declared step timeout, on the CLI and the SDK/MCP path alike; an explicit --timeout replaces it, and --timeout 0 still disables it. A Component without build is packaged as before (#115)
  • The converge_domains MCP tool takes an optional domain: given, domains.yml runs only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exits PRECONDITION (lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now records previousConfigurationSha256, the sha256 of the vhost file the run replaced, or null when none was there; receipts without it still load (#116)
  • cloudfall domains apply <domain> [--issue-certificate] [--yes] converges one Domain: domains.yml runs on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without --yes it exits 0 with a plan. --issue-certificate refuses a Domain with tls.mode: disabled, and first checks on the controller that the primary name and every alias resolve to the proxy server (PRECONDITION, domains_dns_unverified, naming each failing name); a proxied Domain skips the check (dnsCheck: "skipped-proxied"). With --yes it answers the receipt path under --deployments (#117)
  • cloudfall domains observe <domain> reads one Domain on its proxy server alone, through the new read-only domains-observe.yml: the vhost file and its sha256, the certificate's expiry, certbot.timer, and whether the vhost still matches the last receipt (receipt: null before the first). It changes nothing on the server or in the project, and a missing vhost exits 0. cloudfall mcp serve lists domains_apply (with its yes gate) and domains_observe as tools (#118)
  • Components: a release.command (with optional workingDirectory and timeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server of deployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes or current moves; it runs as the application's user with the component's env file loaded under systemd's EnvironmentFile= rules. A non-zero exit or a timeout fails the deploy with ENGINE_STEP_FAILED before any server switches, and a passing run is recorded as releaseCommand (server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119)
    -...
Read more

cloudfall 0.8.0rc86

cloudfall 0.8.0rc86 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Nov 19:48

Changes since v0.7.0:

Breaking

  • deploy --yes and migrate --yes on an application that declares approval: manual now need a person's approval of the release: without a cloudfall release approve record that counts (the same archive SHA-256, exactly the component's declared servers, not expired), deploy --yes exits 4 PRECONDITION with deployment_approval_missing before any playbook runs, naming the release approve command, and lists each record that doesn't count with digest_mismatch, servers_changed or expired. This hits every project that declares manual and deploys today, the example crm.yaml and every Render import included. Two ways out: keep manual and approve each release first (build it, run cloudfall release approve at a terminal, commit the record under decisions/releases/ when CI deploys, then deploy), or switch the application to approval: automatic when another gate, such as GitHub's required reviewers, is the real one. The deploy plan and result gain approval (policy, and for manual the status, the counting record's path, approver and expires_at or approved_at, the records that don't count and the command to run), deploy gains --approvals (default decisions/releases) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval, and cloudfall mcp serve binds the approvals folder (its own --approvals) so a deploy call can't name its own; an automatic application's deploy never reads the folder (#163)
  • A LoggingStack now needs a storage pool on its backend's baseline: cloudfall config validate refuses a LoggingStack whose backend server's Baseline declares no storage.pools with CONFIG_INVALID and code volume_requirement_pool_missing, so a project whose LoggingStack validated 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.pools with id, volumeGroup and primary); with more than one pool, name it on each volume in spec.backend.storage.pool and spec.metrics.backend.storagePool, or validation refuses with volume_requirement_pool_ambiguous (S-014-2)
  • cloudfall config validate refuses one SSH key (same type and body, any comment) declared active and revoked in the same environment, with CONFIG_INVALID and code ssh_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 one revoked if it should not (#354)
  • Some source URLs that cloudfall data copy and cloudfall migrate --data read through --dbname before 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, with lifecycle_execution_failed and 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 serve in a project, a confirmed call of deploy, rollback, restart, migrate, data_copy or domains_apply (yes: true), or of converge_baseline, converge_services or converge_domains (confirm_destructive: true), now runs only when an OperatorPolicy grant covers it in every environment the run touches. Any other confirmed call runs nothing: it answers PRECONDITION with error.context.code: operator_approval_required, context.proposal (the id of a proposed agent 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) and context.reasons (one line per environment, naming why no grant covers it). The same call made again while that proposal is proposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as a migrate whose pending steps are builds and controller steps like ttl-lower, touches no environment whose grant could cover it, so it always proposes: its record's operation.servers and operation.environments are empty (the OperatorProposal schema now accepts empty lists there) and its reason says only a person approves it. A converge_* call that refuses itself before any playbook, such as converge_domains for an undeclared Domain, still refuses as before and writes no record. With no OperatorPolicy declared every confirmed call proposes; to keep the one-call flow in an environment, declare an OperatorPolicy for it whose spec.autonomy.operations grants those classes (deploy, rollback, restart, migrate, data-copy, domains-apply, converge-baseline, converge-services, converge-domains) and earn its requiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008's deployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan's approval.selfConfirm tells an agent in advance. A migrate with no pending step left still answers complete and writes no record, since there is nothing to run. On the CLI, a command without --proposals runs as before (cloudfall deploy --yes in a shell runs the deploy), while one given --proposals and --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 a workingDirectory inside the packaged root, an argv command and an optional timeoutSeconds from 1 to 3600, default 900) and spec.artifact.include (relative paths the build produces); cloudfall config validate refuses a step whose command[0] is not in buildTools (component_build_tool_undeclared), an absolute or .. path, and buildTools or artifact without build. Validation only: artifact build does not run the steps yet. Components without build validate as before (#113)
  • cloudfall-engine artifact build runs a Component's declared spec.build steps on the controller before packaging: it checks every spec.buildTools entry is on PATH at its minimum version before cloning (artifact_build_tool_missing, artifact_build_tool_unsupported), runs each step in the clean checkout with only PATH, HOME, LANG, TMPDIR and CI=true in its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its own timeoutSeconds (artifact_build_step_failed), a missing include path (artifact_include_missing), an include path that leads out of the checkout through a symlink (artifact_include_outside_checkout) or a tracked file a step deleted (artifact_tracked_file_missing), packages the tracked files plus every spec.artifact.include path (a gitignored web/dist, say), and records the steps and tool versions as the new optional spec.build of the Artifact metadata. The command's time limit is now the clone time (1800 seconds) plus every declared step timeout, on the CLI and the SDK/MCP path alike; an explicit --timeout replaces it, and --timeout 0 still disables it. A Component without build is packaged as before (#115)
  • The converge_domains MCP tool takes an optional domain: given, domains.yml runs only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exits PRECONDITION (lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now records previousConfigurationSha256, the sha256 of the vhost file the run replaced, or null when none was there; receipts without it still load (#116)
  • cloudfall domains apply <domain> [--issue-certificate] [--yes] converges one Domain: domains.yml runs on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without --yes it exits 0 with a plan. --issue-certificate refuses a Domain with tls.mode: disabled, and first checks on the controller that the primary name and every alias resolve to the proxy server (PRECONDITION, domains_dns_unverified, naming each failing name); a proxied Domain skips the check (dnsCheck: "skipped-proxied"). With --yes it answers the receipt path under --deployments (#117)
  • cloudfall domains observe <domain> reads one Domain on its proxy server alone, through the new read-only domains-observe.yml: the vhost file and its sha256, the certificate's expiry, certbot.timer, and whether the vhost still matches the last receipt (receipt: null before the first). It changes nothing on the server or in the project, and a missing vhost exits 0. cloudfall mcp serve lists domains_apply (with its yes gate) and domains_observe as tools (#118)
  • Components: a release.command (with optional workingDirectory and timeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server of deployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes or current moves; it runs as the application's user with the component's env file loaded under systemd's EnvironmentFile= rules. A non-zero exit or a timeout fails the deploy with ENGINE_STEP_FAILED before any server switches, and a passing run is recorded as releaseCommand (server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119)
    -...
Read more

cloudfall 0.8.0rc85

cloudfall 0.8.0rc85 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Nov 18:56

Changes since v0.7.0:

Breaking

  • deploy --yes and migrate --yes on an application that declares approval: manual now need a person's approval of the release: without a cloudfall release approve record that counts (the same archive SHA-256, exactly the component's declared servers, not expired), deploy --yes exits 4 PRECONDITION with deployment_approval_missing before any playbook runs, naming the release approve command, and lists each record that doesn't count with digest_mismatch, servers_changed or expired. This hits every project that declares manual and deploys today, the example crm.yaml and every Render import included. Two ways out: keep manual and approve each release first (build it, run cloudfall release approve at a terminal, commit the record under decisions/releases/ when CI deploys, then deploy), or switch the application to approval: automatic when another gate, such as GitHub's required reviewers, is the real one. The deploy plan and result gain approval (policy, and for manual the status, the counting record's path, approver and expires_at or approved_at, the records that don't count and the command to run), deploy gains --approvals (default decisions/releases) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval, and cloudfall mcp serve binds the approvals folder (its own --approvals) so a deploy call can't name its own; an automatic application's deploy never reads the folder (#163)
  • A LoggingStack now needs a storage pool on its backend's baseline: cloudfall config validate refuses a LoggingStack whose backend server's Baseline declares no storage.pools with CONFIG_INVALID and code volume_requirement_pool_missing, so a project whose LoggingStack validated 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.pools with id, volumeGroup and primary); with more than one pool, name it on each volume in spec.backend.storage.pool and spec.metrics.backend.storagePool, or validation refuses with volume_requirement_pool_ambiguous (S-014-2)
  • cloudfall config validate refuses one SSH key (same type and body, any comment) declared active and revoked in the same environment, with CONFIG_INVALID and code ssh_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 one revoked if it should not (#354)
  • Some source URLs that cloudfall data copy and cloudfall migrate --data read through --dbname before 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, with lifecycle_execution_failed and 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 serve in a project, a confirmed call of deploy, rollback, restart, migrate, data_copy or domains_apply (yes: true), or of converge_baseline, converge_services or converge_domains (confirm_destructive: true), now runs only when an OperatorPolicy grant covers it in every environment the run touches. Any other confirmed call runs nothing: it answers PRECONDITION with error.context.code: operator_approval_required, context.proposal (the id of a proposed agent 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) and context.reasons (one line per environment, naming why no grant covers it). The same call made again while that proposal is proposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as a migrate whose pending steps are builds and controller steps like ttl-lower, touches no environment whose grant could cover it, so it always proposes: its record's operation.servers and operation.environments are empty (the OperatorProposal schema now accepts empty lists there) and its reason says only a person approves it. A converge_* call that refuses itself before any playbook, such as converge_domains for an undeclared Domain, still refuses as before and writes no record. With no OperatorPolicy declared every confirmed call proposes; to keep the one-call flow in an environment, declare an OperatorPolicy for it whose spec.autonomy.operations grants those classes (deploy, rollback, restart, migrate, data-copy, domains-apply, converge-baseline, converge-services, converge-domains) and earn its requiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008's deployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan's approval.selfConfirm tells an agent in advance. A migrate with no pending step left still answers complete and writes no record, since there is nothing to run. On the CLI, a command without --proposals runs as before (cloudfall deploy --yes in a shell runs the deploy), while one given --proposals and --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 a workingDirectory inside the packaged root, an argv command and an optional timeoutSeconds from 1 to 3600, default 900) and spec.artifact.include (relative paths the build produces); cloudfall config validate refuses a step whose command[0] is not in buildTools (component_build_tool_undeclared), an absolute or .. path, and buildTools or artifact without build. Validation only: artifact build does not run the steps yet. Components without build validate as before (#113)
  • cloudfall-engine artifact build runs a Component's declared spec.build steps on the controller before packaging: it checks every spec.buildTools entry is on PATH at its minimum version before cloning (artifact_build_tool_missing, artifact_build_tool_unsupported), runs each step in the clean checkout with only PATH, HOME, LANG, TMPDIR and CI=true in its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its own timeoutSeconds (artifact_build_step_failed), a missing include path (artifact_include_missing), an include path that leads out of the checkout through a symlink (artifact_include_outside_checkout) or a tracked file a step deleted (artifact_tracked_file_missing), packages the tracked files plus every spec.artifact.include path (a gitignored web/dist, say), and records the steps and tool versions as the new optional spec.build of the Artifact metadata. The command's time limit is now the clone time (1800 seconds) plus every declared step timeout, on the CLI and the SDK/MCP path alike; an explicit --timeout replaces it, and --timeout 0 still disables it. A Component without build is packaged as before (#115)
  • The converge_domains MCP tool takes an optional domain: given, domains.yml runs only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exits PRECONDITION (lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now records previousConfigurationSha256, the sha256 of the vhost file the run replaced, or null when none was there; receipts without it still load (#116)
  • cloudfall domains apply <domain> [--issue-certificate] [--yes] converges one Domain: domains.yml runs on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without --yes it exits 0 with a plan. --issue-certificate refuses a Domain with tls.mode: disabled, and first checks on the controller that the primary name and every alias resolve to the proxy server (PRECONDITION, domains_dns_unverified, naming each failing name); a proxied Domain skips the check (dnsCheck: "skipped-proxied"). With --yes it answers the receipt path under --deployments (#117)
  • cloudfall domains observe <domain> reads one Domain on its proxy server alone, through the new read-only domains-observe.yml: the vhost file and its sha256, the certificate's expiry, certbot.timer, and whether the vhost still matches the last receipt (receipt: null before the first). It changes nothing on the server or in the project, and a missing vhost exits 0. cloudfall mcp serve lists domains_apply (with its yes gate) and domains_observe as tools (#118)
  • Components: a release.command (with optional workingDirectory and timeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server of deployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes or current moves; it runs as the application's user with the component's env file loaded under systemd's EnvironmentFile= rules. A non-zero exit or a timeout fails the deploy with ENGINE_STEP_FAILED before any server switches, and a passing run is recorded as releaseCommand (server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119)
    -...
Read more

cloudfall 0.8.0rc84

cloudfall 0.8.0rc84 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Nov 16:26

Changes since v0.7.0:

Breaking

  • deploy --yes and migrate --yes on an application that declares approval: manual now need a person's approval of the release: without a cloudfall release approve record that counts (the same archive SHA-256, exactly the component's declared servers, not expired), deploy --yes exits 4 PRECONDITION with deployment_approval_missing before any playbook runs, naming the release approve command, and lists each record that doesn't count with digest_mismatch, servers_changed or expired. This hits every project that declares manual and deploys today, the example crm.yaml and every Render import included. Two ways out: keep manual and approve each release first (build it, run cloudfall release approve at a terminal, commit the record under decisions/releases/ when CI deploys, then deploy), or switch the application to approval: automatic when another gate, such as GitHub's required reviewers, is the real one. The deploy plan and result gain approval (policy, and for manual the status, the counting record's path, approver and expires_at or approved_at, the records that don't count and the command to run), deploy gains --approvals (default decisions/releases) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval, and cloudfall mcp serve binds the approvals folder (its own --approvals) so a deploy call can't name its own; an automatic application's deploy never reads the folder (#163)
  • A LoggingStack now needs a storage pool on its backend's baseline: cloudfall config validate refuses a LoggingStack whose backend server's Baseline declares no storage.pools with CONFIG_INVALID and code volume_requirement_pool_missing, so a project whose LoggingStack validated 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.pools with id, volumeGroup and primary); with more than one pool, name it on each volume in spec.backend.storage.pool and spec.metrics.backend.storagePool, or validation refuses with volume_requirement_pool_ambiguous (S-014-2)
  • cloudfall config validate refuses one SSH key (same type and body, any comment) declared active and revoked in the same environment, with CONFIG_INVALID and code ssh_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 one revoked if it should not (#354)
  • Some source URLs that cloudfall data copy and cloudfall migrate --data read through --dbname before 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, with lifecycle_execution_failed and 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 serve in a project, a confirmed call of deploy, rollback, restart, migrate, data_copy or domains_apply (yes: true), or of converge_baseline, converge_services or converge_domains (confirm_destructive: true), now runs only when an OperatorPolicy grant covers it in every environment the run touches. Any other confirmed call runs nothing: it answers PRECONDITION with error.context.code: operator_approval_required, context.proposal (the id of a proposed agent 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) and context.reasons (one line per environment, naming why no grant covers it). The same call made again while that proposal is proposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as a migrate whose pending steps are builds and controller steps like ttl-lower, touches no environment whose grant could cover it, so it always proposes: its record's operation.servers and operation.environments are empty (the OperatorProposal schema now accepts empty lists there) and its reason says only a person approves it. A converge_* call that refuses itself before any playbook, such as converge_domains for an undeclared Domain, still refuses as before and writes no record. With no OperatorPolicy declared every confirmed call proposes; to keep the one-call flow in an environment, declare an OperatorPolicy for it whose spec.autonomy.operations grants those classes (deploy, rollback, restart, migrate, data-copy, domains-apply, converge-baseline, converge-services, converge-domains) and earn its requiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008's deployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan's approval.selfConfirm tells an agent in advance. A migrate with no pending step left still answers complete and writes no record, since there is nothing to run. On the CLI, a command without --proposals runs as before (cloudfall deploy --yes in a shell runs the deploy), while one given --proposals and --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 a workingDirectory inside the packaged root, an argv command and an optional timeoutSeconds from 1 to 3600, default 900) and spec.artifact.include (relative paths the build produces); cloudfall config validate refuses a step whose command[0] is not in buildTools (component_build_tool_undeclared), an absolute or .. path, and buildTools or artifact without build. Validation only: artifact build does not run the steps yet. Components without build validate as before (#113)
  • cloudfall-engine artifact build runs a Component's declared spec.build steps on the controller before packaging: it checks every spec.buildTools entry is on PATH at its minimum version before cloning (artifact_build_tool_missing, artifact_build_tool_unsupported), runs each step in the clean checkout with only PATH, HOME, LANG, TMPDIR and CI=true in its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its own timeoutSeconds (artifact_build_step_failed), a missing include path (artifact_include_missing), an include path that leads out of the checkout through a symlink (artifact_include_outside_checkout) or a tracked file a step deleted (artifact_tracked_file_missing), packages the tracked files plus every spec.artifact.include path (a gitignored web/dist, say), and records the steps and tool versions as the new optional spec.build of the Artifact metadata. The command's time limit is now the clone time (1800 seconds) plus every declared step timeout, on the CLI and the SDK/MCP path alike; an explicit --timeout replaces it, and --timeout 0 still disables it. A Component without build is packaged as before (#115)
  • The converge_domains MCP tool takes an optional domain: given, domains.yml runs only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exits PRECONDITION (lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now records previousConfigurationSha256, the sha256 of the vhost file the run replaced, or null when none was there; receipts without it still load (#116)
  • cloudfall domains apply <domain> [--issue-certificate] [--yes] converges one Domain: domains.yml runs on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without --yes it exits 0 with a plan. --issue-certificate refuses a Domain with tls.mode: disabled, and first checks on the controller that the primary name and every alias resolve to the proxy server (PRECONDITION, domains_dns_unverified, naming each failing name); a proxied Domain skips the check (dnsCheck: "skipped-proxied"). With --yes it answers the receipt path under --deployments (#117)
  • cloudfall domains observe <domain> reads one Domain on its proxy server alone, through the new read-only domains-observe.yml: the vhost file and its sha256, the certificate's expiry, certbot.timer, and whether the vhost still matches the last receipt (receipt: null before the first). It changes nothing on the server or in the project, and a missing vhost exits 0. cloudfall mcp serve lists domains_apply (with its yes gate) and domains_observe as tools (#118)
  • Components: a release.command (with optional workingDirectory and timeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server of deployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes or current moves; it runs as the application's user with the component's env file loaded under systemd's EnvironmentFile= rules. A non-zero exit or a timeout fails the deploy with ENGINE_STEP_FAILED before any server switches, and a passing run is recorded as releaseCommand (server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119)
    -...
Read more

cloudfall 0.8.0rc83

cloudfall 0.8.0rc83 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 18 Nov 22:06

Changes since v0.7.0:

Breaking

  • deploy --yes and migrate --yes on an application that declares approval: manual now need a person's approval of the release: without a cloudfall release approve record that counts (the same archive SHA-256, exactly the component's declared servers, not expired), deploy --yes exits 4 PRECONDITION with deployment_approval_missing before any playbook runs, naming the release approve command, and lists each record that doesn't count with digest_mismatch, servers_changed or expired. This hits every project that declares manual and deploys today, the example crm.yaml and every Render import included. Two ways out: keep manual and approve each release first (build it, run cloudfall release approve at a terminal, commit the record under decisions/releases/ when CI deploys, then deploy), or switch the application to approval: automatic when another gate, such as GitHub's required reviewers, is the real one. The deploy plan and result gain approval (policy, and for manual the status, the counting record's path, approver and expires_at or approved_at, the records that don't count and the command to run), deploy gains --approvals (default decisions/releases) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval, and cloudfall mcp serve binds the approvals folder (its own --approvals) so a deploy call can't name its own; an automatic application's deploy never reads the folder (#163)
  • A LoggingStack now needs a storage pool on its backend's baseline: cloudfall config validate refuses a LoggingStack whose backend server's Baseline declares no storage.pools with CONFIG_INVALID and code volume_requirement_pool_missing, so a project whose LoggingStack validated 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.pools with id, volumeGroup and primary); with more than one pool, name it on each volume in spec.backend.storage.pool and spec.metrics.backend.storagePool, or validation refuses with volume_requirement_pool_ambiguous (S-014-2)
  • cloudfall config validate refuses one SSH key (same type and body, any comment) declared active and revoked in the same environment, with CONFIG_INVALID and code ssh_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 one revoked if it should not (#354)
  • Some source URLs that cloudfall data copy and cloudfall migrate --data read through --dbname before 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, with lifecycle_execution_failed and 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 serve in a project, a confirmed call of deploy, rollback, restart, migrate, data_copy or domains_apply (yes: true), or of converge_baseline, converge_services or converge_domains (confirm_destructive: true), now runs only when an OperatorPolicy grant covers it in every environment the run touches. Any other confirmed call runs nothing: it answers PRECONDITION with error.context.code: operator_approval_required, context.proposal (the id of a proposed agent 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) and context.reasons (one line per environment, naming why no grant covers it). The same call made again while that proposal is proposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as a migrate whose pending steps are builds and controller steps like ttl-lower, touches no environment whose grant could cover it, so it always proposes: its record's operation.servers and operation.environments are empty (the OperatorProposal schema now accepts empty lists there) and its reason says only a person approves it. A converge_* call that refuses itself before any playbook, such as converge_domains for an undeclared Domain, still refuses as before and writes no record. With no OperatorPolicy declared every confirmed call proposes; to keep the one-call flow in an environment, declare an OperatorPolicy for it whose spec.autonomy.operations grants those classes (deploy, rollback, restart, migrate, data-copy, domains-apply, converge-baseline, converge-services, converge-domains) and earn its requiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008's deployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan's approval.selfConfirm tells an agent in advance. A migrate with no pending step left still answers complete and writes no record, since there is nothing to run. On the CLI, a command without --proposals runs as before (cloudfall deploy --yes in a shell runs the deploy), while one given --proposals and --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 a workingDirectory inside the packaged root, an argv command and an optional timeoutSeconds from 1 to 3600, default 900) and spec.artifact.include (relative paths the build produces); cloudfall config validate refuses a step whose command[0] is not in buildTools (component_build_tool_undeclared), an absolute or .. path, and buildTools or artifact without build. Validation only: artifact build does not run the steps yet. Components without build validate as before (#113)
  • cloudfall-engine artifact build runs a Component's declared spec.build steps on the controller before packaging: it checks every spec.buildTools entry is on PATH at its minimum version before cloning (artifact_build_tool_missing, artifact_build_tool_unsupported), runs each step in the clean checkout with only PATH, HOME, LANG, TMPDIR and CI=true in its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its own timeoutSeconds (artifact_build_step_failed), a missing include path (artifact_include_missing), an include path that leads out of the checkout through a symlink (artifact_include_outside_checkout) or a tracked file a step deleted (artifact_tracked_file_missing), packages the tracked files plus every spec.artifact.include path (a gitignored web/dist, say), and records the steps and tool versions as the new optional spec.build of the Artifact metadata. The command's time limit is now the clone time (1800 seconds) plus every declared step timeout, on the CLI and the SDK/MCP path alike; an explicit --timeout replaces it, and --timeout 0 still disables it. A Component without build is packaged as before (#115)
  • The converge_domains MCP tool takes an optional domain: given, domains.yml runs only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exits PRECONDITION (lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now records previousConfigurationSha256, the sha256 of the vhost file the run replaced, or null when none was there; receipts without it still load (#116)
  • cloudfall domains apply <domain> [--issue-certificate] [--yes] converges one Domain: domains.yml runs on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without --yes it exits 0 with a plan. --issue-certificate refuses a Domain with tls.mode: disabled, and first checks on the controller that the primary name and every alias resolve to the proxy server (PRECONDITION, domains_dns_unverified, naming each failing name); a proxied Domain skips the check (dnsCheck: "skipped-proxied"). With --yes it answers the receipt path under --deployments (#117)
  • cloudfall domains observe <domain> reads one Domain on its proxy server alone, through the new read-only domains-observe.yml: the vhost file and its sha256, the certificate's expiry, certbot.timer, and whether the vhost still matches the last receipt (receipt: null before the first). It changes nothing on the server or in the project, and a missing vhost exits 0. cloudfall mcp serve lists domains_apply (with its yes gate) and domains_observe as tools (#118)
  • Components: a release.command (with optional workingDirectory and timeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server of deployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes or current moves; it runs as the application's user with the component's env file loaded under systemd's EnvironmentFile= rules. A non-zero exit or a timeout fails the deploy with ENGINE_STEP_FAILED before any server switches, and a passing run is recorded as releaseCommand (server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119)
    -...
Read more

cloudfall 0.8.0rc82

cloudfall 0.8.0rc82 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 18 Nov 20:21

Changes since v0.7.0:

Breaking

  • deploy --yes and migrate --yes on an application that declares approval: manual now need a person's approval of the release: without a cloudfall release approve record that counts (the same archive SHA-256, exactly the component's declared servers, not expired), deploy --yes exits 4 PRECONDITION with deployment_approval_missing before any playbook runs, naming the release approve command, and lists each record that doesn't count with digest_mismatch, servers_changed or expired. This hits every project that declares manual and deploys today, the example crm.yaml and every Render import included. Two ways out: keep manual and approve each release first (build it, run cloudfall release approve at a terminal, commit the record under decisions/releases/ when CI deploys, then deploy), or switch the application to approval: automatic when another gate, such as GitHub's required reviewers, is the real one. The deploy plan and result gain approval (policy, and for manual the status, the counting record's path, approver and expires_at or approved_at, the records that don't count and the command to run), deploy gains --approvals (default decisions/releases) and the RECORD_INVALID exit for an approvals file that isn't a valid ReleaseApproval, and cloudfall mcp serve binds the approvals folder (its own --approvals) so a deploy call can't name its own; an automatic application's deploy never reads the folder (#163)
  • A LoggingStack now needs a storage pool on its backend's baseline: cloudfall config validate refuses a LoggingStack whose backend server's Baseline declares no storage.pools with CONFIG_INVALID and code volume_requirement_pool_missing, so a project whose LoggingStack validated 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.pools with id, volumeGroup and primary); with more than one pool, name it on each volume in spec.backend.storage.pool and spec.metrics.backend.storagePool, or validation refuses with volume_requirement_pool_ambiguous (S-014-2)
  • cloudfall config validate refuses one SSH key (same type and body, any comment) declared active and revoked in the same environment, with CONFIG_INVALID and code ssh_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 one revoked if it should not (#354)
  • Some source URLs that cloudfall data copy and cloudfall migrate --data read through --dbname before 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, with lifecycle_execution_failed and 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 serve in a project, a confirmed call of deploy, rollback, restart, migrate, data_copy or domains_apply (yes: true), or of converge_baseline, converge_services or converge_domains (confirm_destructive: true), now runs only when an OperatorPolicy grant covers it in every environment the run touches. Any other confirmed call runs nothing: it answers PRECONDITION with error.context.code: operator_approval_required, context.proposal (the id of a proposed agent 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) and context.reasons (one line per environment, naming why no grant covers it). The same call made again while that proposal is proposed, against the same plan, commit and uncommitted changes, returns the same id and writes nothing. A run that changes no declared server, such as a migrate whose pending steps are builds and controller steps like ttl-lower, touches no environment whose grant could cover it, so it always proposes: its record's operation.servers and operation.environments are empty (the OperatorProposal schema now accepts empty lists there) and its reason says only a person approves it. A converge_* call that refuses itself before any playbook, such as converge_domains for an undeclared Domain, still refuses as before and writes no record. With no OperatorPolicy declared every confirmed call proposes; to keep the one-call flow in an environment, declare an OperatorPolicy for it whose spec.autonomy.operations grants those classes (deploy, rollback, restart, migrate, data-copy, domains-apply, converge-baseline, converge-services, converge-domains) and earn its requiredVerifiedRuns. The checks that came first still do and write no record: argument and config validation, S-008's deployment_approval_missing, and a component lock another run holds. The server's instructions say so, and the plan's approval.selfConfirm tells an agent in advance. A migrate with no pending step left still answers complete and writes no record, since there is nothing to run. On the CLI, a command without --proposals runs as before (cloudfall deploy --yes in a shell runs the deploy), while one given --proposals and --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 a workingDirectory inside the packaged root, an argv command and an optional timeoutSeconds from 1 to 3600, default 900) and spec.artifact.include (relative paths the build produces); cloudfall config validate refuses a step whose command[0] is not in buildTools (component_build_tool_undeclared), an absolute or .. path, and buildTools or artifact without build. Validation only: artifact build does not run the steps yet. Components without build validate as before (#113)
  • cloudfall-engine artifact build runs a Component's declared spec.build steps on the controller before packaging: it checks every spec.buildTools entry is on PATH at its minimum version before cloning (artifact_build_tool_missing, artifact_build_tool_unsupported), runs each step in the clean checkout with only PATH, HOME, LANG, TMPDIR and CI=true in its environment and its output on stderr, fails without writing an archive on a non-zero exit or a step outrunning its own timeoutSeconds (artifact_build_step_failed), a missing include path (artifact_include_missing), an include path that leads out of the checkout through a symlink (artifact_include_outside_checkout) or a tracked file a step deleted (artifact_tracked_file_missing), packages the tracked files plus every spec.artifact.include path (a gitignored web/dist, say), and records the steps and tool versions as the new optional spec.build of the Artifact metadata. The command's time limit is now the clone time (1800 seconds) plus every declared step timeout, on the CLI and the SDK/MCP path alike; an explicit --timeout replaces it, and --timeout 0 still disables it. A Component without build is packaged as before (#115)
  • The converge_domains MCP tool takes an optional domain: given, domains.yml runs only on that Domain's proxy server (--limit) and renders only that Domain, and an unknown id exits PRECONDITION (lifecycle_domain_missing) before the inventory render; omitted, it runs on every server as before. Each domain receipt now records previousConfigurationSha256, the sha256 of the vhost file the run replaced, or null when none was there; receipts without it still load (#116)
  • cloudfall domains apply <domain> [--issue-certificate] [--yes] converges one Domain: domains.yml runs on its proxy server alone and renders only it, so no baseline, firewall or service task runs. Without --yes it exits 0 with a plan. --issue-certificate refuses a Domain with tls.mode: disabled, and first checks on the controller that the primary name and every alias resolve to the proxy server (PRECONDITION, domains_dns_unverified, naming each failing name); a proxied Domain skips the check (dnsCheck: "skipped-proxied"). With --yes it answers the receipt path under --deployments (#117)
  • cloudfall domains observe <domain> reads one Domain on its proxy server alone, through the new read-only domains-observe.yml: the vhost file and its sha256, the certificate's expiry, certbot.timer, and whether the vhost still matches the last receipt (receipt: null before the first). It changes nothing on the server or in the project, and a missing vhost exits 0. cloudfall mcp serve lists domains_apply (with its yes gate) and domains_observe as tools (#118)
  • Components: a release.command (with optional workingDirectory and timeoutSeconds, 1 to 1800, default 300) runs once per deploy on the first server of deployment.servers, which now deploys first, after the release's dependencies are materialized and before the unit file changes or current moves; it runs as the application's user with the component's env file loaded under systemd's EnvironmentFile= rules. A non-zero exit or a timeout fails the deploy with ENGINE_STEP_FAILED before any server switches, and a passing run is recorded as releaseCommand (server, command, exit code, last 2000 characters of output) in every release receipt of that deploy (#119)
    -...
Read more