Bundle operations and deployments

Beyond the conceptual bundle model, the product exposes granular organization and project APIs for repositories, bundles, environments, manifests, cluster resources, revisions, deployments, and operations (build, deploy, discover). Each step is durable in the control plane and drives asynchronous automation in the execution tier.

Repository connection

Bundle repositories (organization scope) record Git remotes Loopback may access after OAuth. Browse helpers expose tree endpoints for UI file pickers.

Bundle entity

The bundle entity defines the product identity of an application sourced from Git (name, slug, links to repository).

Environments and manifests

Environments bind a bundle to a target workspace (or cluster resource abstraction). Manifests capture Kubernetes-shaped desired state discovered or edited through the product.

Revisions and deployments

Revisions are immutable snapshots of build outputs (image digests, chart versions). Deployments associate a revision with an environment and track rollout status.

Operations API

Bundle operations trigger long-running work: discover repository structure, build container images, deploy to Kubernetes. Responses return quickly while jobs run; poll deployment or operation records for completion.

Webhook-driven refresh

Git webhooks may re-queue discovery or builds on push events (see Git OAuth and webhooks).