ankra application
Connect application source repositories to Ankra for analysis, packaging, and deployment.ankra application add
Add an application by reading a local Git checkout. The command detects the GitHub repository from the selected remote, uses the remote’s default branch when available, and falls back to the current branch. It selects an available GitHub credential automatically when the choice is unambiguous. Pass —registry-url to have the application publish to a container image registry you already operate instead of the organisation’s own Ankra registry project. Declare it here rather than afterwards: the setup job generates the build workflow from the declaration the application is created with, so a registry added later leaves a workflow that logs in with the wrong one.ankra application ai-config
Read, set, or reset which AI lanes run on this application’s repository (pull request review, demo URL, and the rest), on which model, and within what limits. An application follows the organisation’s defaults until an override is set here.ankra application ai-config clear
Reset the application to the organisation’s AI defaultsankra application ai-config get
Show the application’s effective AI lane configurationankra application ai-config set
Replace the application’s AI lane configuration with a JSON document. Start from the current one: ‘ankra application ai-config get <id> -o json’, edit it, and pass the file back with —file (or ’-’ to read stdin).ankra application auto-deploy
Inspect and set whether pushes to the tracked branch deploy themselves. With auto-deploy on, a build Ankra observes on the application’s tracked branch is rolled out to its deployments unattended. With it off, a push still builds - it just waits for an explicit ‘ankra application deploy’.ankra application auto-deploy get
Show whether auto-deploy is on, and the newest build seen on the tracked branch. The newest observed build comes back with the switch so you can tell an auto-deploy that is off from one that is on but has had nothing to pick up.ankra application auto-deploy set
Turn auto-deploy on or off. —enabled is required and must be given explicitly: turning unattended deployment on and turning it off are both deliberate acts, and neither is a safe default to infer from a bare ‘set’.ankra application branch-files
List the tracked files on the setup branchankra application branches
List the application repository branchesankra application build
Build an application’s image on Ankra’s builders. Ankra clones the commit, resolves a recipe for it (the repository’s own Dockerfile, else a generated one, else buildpacks), builds it, and pushes the image to the registry the application publishes to - without the repository’s CI running at all. The routes answer 404 for organisations without the platform_builds feature flag, which is off by default while the lane rolls out. Ask Ankra support to enable it for your organisation.ankra application build get
Show one platform build. A failed build carries an error_class saying whose failure it was. build_failed is the repository’s - the recipe did not build - and is the one worth reading the error_message for. clone_auth and recipe_missing are the application’s configuration. push_failed, timeout and capacity are Ankra’s, and are already visible to Ankra without anyone reporting them.ankra application build list
List the application’s platform builds, newest firstankra application build request
Show a queued build request and the build it became. ‘start’ answers with a request id before there is a build to read: the build row is created when the scheduler claims the request. This is how a caller follows the gap - status is pending until it is claimed, and build_id names the build from that point on.ankra application build start
Queue a build of the application’s image. —commit is required and must be a full 40- or 64-character commit sha. An abbreviation is refused rather than resolved: the queue deduplicates on the string it is given, so a full sha and its own prefix would be two keys for one commit and build it twice. The queue converges on the commit while a request is live. Asking twice joins one build, and the answer’s already_requested reports that it did. With —wait the command follows the request through to the finished build and exits non-zero if the build failed, so a pipeline step can be exactly “build this commit, and fail if it does not build”.ankra application chart-versions
List an application’s published chart versionsankra application code-security
Show source code security findingsankra application container-security
Show container image vulnerability findingsankra application credential
Inspect and re-bind the GitHub credential an application’s repository calls ride on. An application is bound to one GitHub credential of the organisation; its App installation must reach the repository for builds, deploys and Actions secrets to work. Move an application onto another credential when its installation lost - or never had - access to the repository.ankra application credential get
Show the GitHub credential an application is bound toankra application credential set
Re-bind an application to another GitHub credential of the organisation. The credential must exist. Whether its App installation reaches the repository is reported in the answer (resolved / message) rather than refused, since a re-bind is usually how an application gets off an installation that cannot.ankra application delete
Delete an applicationankra application demo
Deploy, inspect, and stop short-lived demo workspaces for a branch or pull request of an application.ankra application demo build
Check whether a branch has a demo-ready container imageankra application demo config
Read or update the application’s saved demo defaultsankra application demo config get
Show the saved demo defaults (env, database, migration command, extensions)ankra application demo config set
Update the application’s saved demo defaults. The command fetches the current configuration first and applies only the flags you set: —env entries override by name, everything else is carried forward.ankra application demo deploy
Deploy a short-lived demo workspace for a branch or pull request. All flags are optional; only the flags you set are sent, so the backend applies its own defaults for the rest. A monorepo demo runs every recorded component as its own pod by default. —component narrows that to the components you name, and the per-component override flags (—component-tag, —component-port, —component-path) tune one component each. Because selection and overrides ride the same request field, an override may only name a component that —component selects: to tune one component of a full launch, list them all.ankra application demo detail
Show a demo workspace’s record, its components, provisioning steps, and failure detail. The default rendering summarises the demo; -o json or -o yaml emit the full payload, including the resource inventory and the Kubernetes events behind a stalled step.ankra application demo fix
Dispatch the AI pre-setup mission for a failed demoankra application demo fix-build
Fix a branch that has no demo-ready container image. This is what to run when ‘demo build’ reports that no image exists for a branch. Ankra applies its own deterministic fixes first (publish-readiness auto-fix, failed-run rerun, failed-setup retry) and, when those cannot produce an image, dispatches a one-shot mission agent that investigates the repository and opens a pull request with the fix. The answer points at the dispatched mission rather than carrying its result, so follow the agent run it names.ankra application demo list
List the application’s active demo workspaces, one row each, with the components every demo runs. -o json or -o yaml emit the full payload, including the TTL policy and the staging cluster’s status.ankra application demo logs
Fetch a bounded tail of the demo container’s logs. One-shot: the command returns after the fetch instead of following the stream. A multi-component demo runs one pod per component, and without a selector the backend reads whichever pod it finds first. —component picks the pod belonging to that component; —pod addresses one by name (fromankra application demo detail) when a component has more than one.