TerraScale.Deploy.Cli (1.0.72)

Published 2026-09-11 00:52:45 +00:00 by terrascale-bot

Setup this registry from the command line:

dotnet nuget add source --name TerraScale --username your_username --password your_token

To install the package using NuGet, run the following command:

dotnet add package --source TerraScale --version 1.0.72 TerraScale.Deploy.Cli

For more information on the NuGet registry, see the documentation.

Internal TerraScale deployment and Forgejo Actions diagnostics CLI.

TerraScale.Deploy

Internal deployment and CI diagnostics tooling for TerraScale Forgejo Actions.

Commands

terrascale-deploy forgejo failures: inventory failed, running, and cancelled Forgejo action tasks across configured TerraScale repositories.
terrascale-deploy ci validate: validate local workflow and repository policy assumptions before editing or dispatching CI.
terrascale-deploy prepare, restore, tests, build, publish-application, build-image, push-images, publish-manifests, notify-flux-image-deployment, verify-deployment, and deployment-notification: run workflow-facing deployment stages.
terrascale-deploy retention: run generic artifact retention policies.
terrascale-deploy notify discord: post a deploy notification only after a verified rollout.
terrascale-deploy sdk validate: run shared SDK and Pages validation checks.

The CLI accepts explicit tokens through environment variables such as FORGEJO_TOKEN, but it can also fall back to the locally authenticated fj CLI for failure inventory when API credentials are not present.

Release Discovery

The workflow-facing stage commands discover deployable projects dynamically. They scan C# projects, solutions, test projects, package manifests, Dockerfiles, project references, and package file: dependencies, then apply any .terrascale/deploy.json overrides.

C# services use .NET SDK container publishing by default. Package apps and other non-C# services use Dockerfile publishing.

See: