Deployment Details

A release is a deployment execution record. Each one tracks status, timestamps, Terraform changes, application deployments, migration scripts, error logs, and approval status. For the full list of release statuses, see Release statuses.

Viewing release details

Using prompt

Show me the details of the last release to dev in the checkout project.

Using command

raptor get releases -p PROJECT -e ENVIRONMENT

raptor get releases RELEASE_ID -p PROJECT -e ENVIRONMENT

--type filters by release type and accepts either the API enum or the label the console shows, so --type selective and --type "Selective Plan" both work. A release still sitting in the queue has no id yet, so use --trace-id to follow the one you triggered.

New to the CLI? Install it first.

Navigate to the Environments section
Select your environment
Click on the Releases tab
Click on any release to view its details

The release details page shows status, timestamps, time taken, release type, triggered by, Terraform changes, application deployments, migration scripts, error logs, and sign-off status.

CRD-based releases

For CRD-based (Custom Resource Definition) releases, additional phase information is displayed:

Release Template Name: Template used (e.g., "full-plan", "selective-plan", "terraform-apply")
Release Namespace: Kubernetes namespace for the release
Ordered Phases: List of execution phases from the ReleaseTemplate

Release changes

View the resource-level changes applied during a release to understand what was modified.

Each resource change shows:

Resource name and type
Modification type (created, updated, deleted)
Specific fields changed
Previous and new values

Viewing release logs

Release logs provide real-time and historical output from deployment operations.

Using prompt

Show me the logs for the last release to dev in the checkout project.

Using command

raptor logs release -p PROJECT -e ENVIRONMENT RELEASE_ID

The log content is written to a tempfile, and stdout shows the file path plus the final status. Add --stream to tee every line to stdout as well, and --follow to keep streaming while the release is still running.

New to the CLI? Install it first.

Open a release from the Releases tab
Click the Logs button
View the paginated log output

Logs are grouped under the blueprint resource they belong to, so the Terraform modules invoked during a release sit under the resource that owns them. Each resource is annotated with its module type, which separates what Facets manages from what your own blueprint defines. A module that is blocked or waiting, whether on inputs, migrations, or dependencies, says so in its own log message rather than going quiet. The search bar filters across the whole log.

For active releases, logs stream in real-time, with status transitions reflected as they happen, and automatic timeout handling to prevent connection issues.

CRD phase logs

For CRD-based releases, view logs for specific execution phases:

Open the release details.
Click the Logs tab.
Select a phase from the dropdown (for example "init", "plan", "apply").
View the logs for that phase.

Each phase has separate log streams for granular troubleshooting.

Streaming logs use an automatic timeout and send keep-alive data to prevent client disconnections during long-running operations.

Log entries include a deploymentType field with values REGULAR (standard deployment), CUSTOM (custom deployment workflow), and ROLLBACK (rollback operation).

Artifact tracking

Releases maintain relationships to artifacts (container images, build outputs) deployed during execution.

Each release tracks:

Artifact URI: Location of deployed artifact
Build ID: Associated build identifier
Stack Name: Stack containing the artifact
App Name: Application name
Registration Metadata: Artifact registration details

The ResourceStatus model tracks per-resource deployment state:

Current BP Version vs Live BP Version: Blueprint version comparison
Current Artifact URL vs Live Artifact URL: Deployed artifact comparison
Sync Status: IN_SYNC or OUT_OF_SYNC
Release Status: QUEUED, FAILED, IN_PROGRESS, or COMPLETED
Health Status: Application health state