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.

Inputs

• 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.

Verify it

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.