Customer setup

After publishing a release, create a deployment group and generate a setup link. Send the link to the person who owns the target environment.

alien onboard "Acme" \
  --external-id org_123 \
  --setup-items application

In the dashboard, use Deployments → New deployment → Generate deployment link. Choose only the platforms and setup items your project supports.

The environment owner opens the link, chooses a setup method, supplies their environment values, and runs the generated setup. Your application does not need their long-lived cloud credentials.

InputsCopy Anchor Link

• Developer-provided values are supplied when you create the link.
• Deployer-provided values are supplied by the environment owner during setup.

Declare which side supplies each value in alien.ts. Test the generated setup and permissions before sending the link.

Accepting a quota warningCopy Anchor Link

If setup reports a quota shortfall, review its usage, required capacity, and increase link before retrying. The project-branded deploy CLI accepts a per-deployment override using the exact quota identity from that error. For the unbranded binary:

alien-deploy deploy --quota-warning-override L-1216C47A

Use your project's binary name in place of alien-deploy and keep the original deployment arguments. The check still runs, but a failure for that identity becomes a visible warning. Provisioning can still fail if the cloud rejects it.

The override persists. Repeat the flag to supply the complete replacement list, or use --clear-quota-warning-overrides to remove all overrides. Omitting both flags preserves the saved list. Unknown identities and identities from another cloud are rejected. Run the branded CLI's status command to see saved overrides; status --json includes quotaWarningOverrides.

The branded CLI also accepts the list in the TOML file passed with --config:

quotaWarningOverrides = ["L-1216C47A"]

An explicit empty list clears overrides; omitting the setting preserves them. Command-line override flags take precedence over this setting. Hosted deployments support changes when the current operation allows settings updates. Standalone-manager deployments accept override changes while running or after a preflight failure when no execution owns them. Apply compute changes separately; older managers that lack the settings endpoint reject the update before retrying. See Quota checks and warning overrides for the alien deploy equivalent and compute blocking policy.

Verify itCopy Anchor Link

Open the deployment in the dashboard and confirm its status and last check-in. Then run one safe Command or request that exercises the path your product depends on.

For automation, wait for the deployment instead of writing your own polling loop:

alien deployments wait acme/production \
  --for ready \
  --timeout 10m \
  --json

See Deployment Portal, Inputs, and Releases.