Skip to main content
Connect aireg to Atlan Trident when you want to install workspace skills or publish from a terminal. You need an Atlan user account and access to the destination workspace. For CI publishing, use a workspace-scoped API key as described under Use an API key in CI.

Before you begin

Install aireg using the project’s installation and access information. The examples use a registry alias named atlan. If your organization uses another Gateway address, substitute the address your administrator provides.
1

Install Atlan adapter

Confirm that atlan appears in the list. The CLI verifies the adapter’s signed release before loading it.
2

Sign in

Sign in through your browser:
The CLI opens Atlan’s sign-in page and prints the link in case the browser doesn’t open. It waits up to five minutes for you to finish; press Ctrl+C to stop waiting. Over SSH, it prints the link and an ssh -L command that forwards its port instead of opening a browser. Browser sign-in needs aireg 0.1.9 or later and is available for https://api.atlan.com and https://api.atlan.dev.For another Gateway address, load your user bearer token from an approved secret store into ATLAN_TOKEN, then pass it on standard input:
--address declares the registry in your user scope if needed. Use the Gateway origin without /registry/v1 or another path. The adapter accepts credential-free HTTPS addresses on Atlan domains.Sign-in onboards a person, so sign in as yourself or use a user token here. Use a service account’s API key through the CI variable below. The CLI stores credentials for this registry alias and origin; another alias has its own account.A browser sign-in renews itself without Atlan Trident Desktop. A piped user token can be refreshed when a matching Atlan Trident Desktop session is available on the same machine; a copied bearer token alone does not provide a refresh session. See Sign-in and tokens.
3

Find workspace skills

Each visible workspace is a namespace. Use the workspace name shown by the command when installing:
Atlan Trident serves the selected channel’s installable release of each skill. Archived versions and versions awaiting approval or scanning do not install. An @<version> pin installs only while it names the release Atlan Trident serves; a pin on any other version fails with the release to move to.
4

Preview and publish skill

From a project containing skills/release-notes/SKILL.md, preview the destination and changes:
Check the workspace in the preview, then publish:
Atlan Trident accepts skills through this publishing path. Each changed skill creates a version. Check the skill in Atlan Trident for its scan and approval status before expecting other people to install it.

Use API key in CI

Set AIREG_TOKEN_ATLAN from your CI secret store for a registry named atlan. The CLI uses it for the command without storing it. Declare the registry before publishing, and use --yes after reviewing the dry run:
The variable follows the registry alias, so another alias needs its matching AIREG_TOKEN_<NAME>. It takes precedence over a stored credential. Background jobs do not inherit this command’s variable; they need a stored account. For a complete workflow with pinned installation and branch controls, see Sync skills from GitHub.

Verify access

A successful sign-in confirms the account. Listing the registry confirms you can read its current catalog. A publish confirms that the server accepted a version; inspect that version’s scan and approval in Atlan Trident to confirm it is installable. If a command fails, see Atlan CLI errors.