Kanject.Cli 1.3.0

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet tool install --global Kanject.Cli --version 1.3.0
                    
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest
                    
if you are setting up this repo
dotnet tool install --local Kanject.Cli --version 1.3.0
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=Kanject.Cli&version=1.3.0
                    
nuke :add-package Kanject.Cli --version 1.3.0
                    

Kanject.Cli

A single .NET global tool that drives C# AWS services from dotnet new to kanject aws deploy --env prod — wrapping the existing dotnet/AWS toolchain so your inner loop stays vanilla and the Lambda, ECS Fargate, static-site, and coupled full-stack deploy plumbing disappears behind one committed manifest.

Install

dotnet tool install --global Kanject.Cli

Requires the .NET 10 SDK. The aws, msbuild, and github providers ship in the box — no extra installs.

Choose a workflow

  • Deploy applications: Lambda, ECS Fargate, or a coupled SPA/backend. Choose independent service roots, a shared multi-Lambda stack, or a coordinated frontend/backend pair.
  • Publish libraries: kanject packages init, then kanject packages plan and kanject packages verify from the package repository root.
  • Distribute desktop apps: initialize the product manifest, register with kanject add distributable, and configure delivery destinations.

Start at Getting started for workflow selection. Service commands run from the directory containing that service's manifest, which can differ from the repository or solution root. The current static-site shape requires a coupled backend.

Discover commands with kanject --help and kanject aws --help.

What it does

  • Bootstrap — dotnet new + kanject init puts the manifest, NuGet config, and dotnet-tool pinning in place in one step.
  • Deploy — kanject aws deploy --env <stage> resolves cross-repo dependencies and env, builds the provider artifacts, and ships the manifest's target (Lambda, ECS Fargate, static site, or a coupled backend + site), recording every release in an S3 deployment ledger.
  • Rollback — kanject aws rollback --env prod shows the last 10 deployments with dates, statuses, targets, and commit summaries; pick one and Kanject does the target-native promotion with the prior artifact still immutable in S3/ECR.
  • And more — cross-repo dependency sync, a local test runner, env/param/secret management, static-site preview environments, VPC & custom-domain wiring, multi-function services, and AWS-native pipeline scaffolding.

It invokes — never replaces — dotnet new, dotnet build, and dotnet lambda, and drives AWS services through their SDK APIs (including CloudFormation change sets). The dotnet-native experience stays; kanject only owns the AWS plumbing that doesn't have a great answer in the box.

Learn more

License

Commercial — governed by the Kanject Code Libraries License Agreement (KCLLA); see the bundled LICENSE.md. © Kanject Business Solutions.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last Updated
2.5.0 103 11/16/2026
2.4.0 93 11/16/2026
2.3.0 113 11/15/2026
2.2.0 128 11/14/2026
2.1.0 96 11/13/2026
2.0.2 102 11/13/2026
2.0.1 94 11/13/2026
2.0.0 100 11/12/2026
1.5.1 123 11/11/2026
1.5.0 121 11/10/2026
1.4.0 106 11/4/2026
1.3.0 119 11/2/2026
1.2.0 157 11/1/2026
1.1.0 115 11/1/2026
1.0.79 111 10/30/2026
1.0.78 101 10/30/2026
1.0.77 108 10/29/2026
1.0.76 102 10/29/2026
1.0.75 100 10/29/2026
1.0.74 101 10/28/2026
Loading failed

- The release Build can skip the gates its rehearsal already ran.
 `aws pipeline promote --verify-only --attestation-out <file>` writes whether the commit's rehearsal recorded its gates (`KANJECT_GATES`), and a new optional `rehearsal.computeType` lets the Build run on smaller compute than the rehearsal (proposal 0055).

- Smaller tool package, same behaviour.
 The `Kanject.Cli` nupkg loses about 1.5 MB (12.8 MB → 11.4 MB) and the installed tool about 5 MB. Three things stop shipping, none of which the running CLI ever loaded: the second copy of `System.Security.Cryptography.Pkcs`, `Microsoft.Bcl.Cryptography` and `System.Formats.Asn1` under every `providers/<key>/` (only the host-shared `Kanject.Cli.Abstractions` references them, so plugins already resolved the host's copy), the XML documentation files, and the host's own unused `Spectre.Console.Json` (the AWS provider keeps the copy its `deployments show` panel uses).