Sign in
Deployed and supported. The fields and commands described here are stable within version v1alpha1.
In three commands, you are authenticated and positioned on a tenant ready to receive your manifests.
1. Sign in
sng sso login
The CLI opens your browser on the StackNGO sign-in page (auth.dev.stackngo.app),
then retrieves the token through a local callback on 127.0.0.1. Nothing to copy and paste.
Ouvrez votre navigateur : https://auth.dev.stackngo.app/login/oauth/authorize?...
connecté : jane (jane@example.com)
Check who you are:
sng sso whoami
organization: stackngo
username: jane
email: jane@example.com
roles: -
Your StackNGO account is created when you register with the StackNGO team. Self-registration is not open for now.
2. Create a tenant, or join one
A tenant is created in one command. Its name becomes your subdomain: keep it short, lowercase, without special characters.
sng tenant create acme
The CLI confirms the creation and tells you what to do next:
next: sng tenant use acme
Your administrator rights on the new tenant are active within one to two minutes.
Some names are reserved and some are already taken: the command tells you immediately (see Reserved names).
If someone has given you access to an existing tenant, it appears in the list:
sng tenant list
TENANT POLICIES CURRENT
acme assume-role,admin
labs assume-role,readonly
3. Choose the current tenant
sng tenant use acme
current tenant: acme
A newly created tenant may take a minute or two to become usable: the CLI
waits and retries on its own (up to six minutes) while displaying policies pending.
4. Cluster and tenant
The CLI talks to one cluster and one tenant. The tenant is the one you just chose; the default cluster is fine to start. Check:
sng config create # creates ~/.config/stackngo/config.yaml
sng config show
cluster: (default)
tenant: acme-dev
api_url: https://api.dev.stackngo.fr
To target another cluster: sng config use-cluster NAME. An environment is a tenant: create
acme-dev and acme-prod and switch between them with sng tenant use (see
Environments and restore).
What if I manage several tenants?
sng tenant use changes the current tenant. To act occasionally on another tenant without
changing sessions, sng tenant assume <tenant> opens a temporary session (you must
hold the assume-role policy there). See sng tenant.
Sign out
sng sso logout
signed out
Local tokens are erased and every tenant session opened with your account ends, on this
machine as elsewhere (another terminal, a copy in a script), within a few seconds. An ended
session is refused (401): you have to sign in again (sng sso login, then
sng tenant use).
Next step: First application.