Trino app image and versioning

||Connect docs via MCP

This page identifies the container image that powers the Trino assets app and explains how that image is versioned. Use it as vendor evidence when registering the software with a governance or procurement process, and to pin the exact version running for your tenant.

Vendor, product, and image

The Trino assets app is distributed as a single container image:

Field	Value
Vendor	Atlan
Product name	Trino assets app
Container image	atlanhq/atlan-trino-app
Registry	Docker Hub, under the private atlanhq/* namespace
Release identifier (version)	Image tag in main-<git-sha> format—for example, main-94f853f

The atlanhq/atlan-trino-app repository is private. Pulling the image requires the Docker Hub Personal Access Token (PAT) that your Atlan representative provides. The PAT is rotated periodically.

How versioning works

The image tag is the canonical, official release identifier for the Trino assets app. Tags follow the main-<git-sha> format, where <git-sha> is the short Git commit hash of the source build—for example, atlanhq/atlan-trino-app:main-94f853f. Each tag is immutable and maps one-to-one to a specific build.

Atlan releases aren't time-boxed, and new versions roll out to tenants in cohorts rather than to the entire fleet at once. As a result:

• Multiple tags of the Trino app image can be current across different tenants at the same time.
• The exact tag deployed for a given tenant is determined dynamically and can change as bug fixes and connector enhancements ship.

To register a point-in-time version, read the exact tag currently deployed for your tenant (see the next section). If the deployed version changes later, re-register the new tag—the versioning scheme itself (main-<git-sha>) doesn't change.

Find exact version deployed for your tenant

You can determine the exact image tag running for your tenant in two ways.

From the Atlan UI

1. Log in to your Atlan tenant.
2. Open the connector marketplace.
3. Select the Trino app.
4. Download the Self-Deployed Runtime (SDR) config. The config lists the image reference, including its tag.

From the API

Call the latest-releases endpoint for your tenant. This requires a valid Atlan API token:

curl -sS \
  -H "Authorization: Bearer $ATLAN_API_TOKEN" \
  "https://<your-tenant>.atlan.com/api/service/marketplace/latest-releases"

The response lists each app's current image as a repo:tag reference under image:

{
  "releases": [
    {
      "app_name": "trino",
      "version": "main-94f853f",
      "image": "atlanhq/atlan-trino-app:main-94f853f"
    }
  ]
}

The image field is the exact, point-in-time version deployed for your tenant.

Verify the image

Atlan signs every Self-Deployed Runtime image with keyless Cosign. Before you deploy or mirror an image, verify its signature using the tag you found earlier—see Verify container images.