Skip to main content
Most IDYL commands run inside an account and use a saved CLI context. A context keeps the selections needed for normal CLI use: Network, identity, account, profile, Namespace, optional Workspace, and Subnet. Use idyl whoami, idyl use, or idyl context show to review the active context before creating or changing resources.

​
Identity

An identity is the authenticated user or token used for a request. Interactive users normally authenticate with idyl login. Automation can use tokens created through IAM. The identity determines who is asking IDYL to perform an action.

​
Account

An account is the primary ownership boundary for IDYL resources. Workload resources, namespaces, subnets, fleets, and IAM configuration are evaluated in relation to an account. A user can have access to more than one account. Accounts are global. Regional placement is selected through subnets, not by creating separate regional accounts.

​
Profile

A profile defines the permissions available when you act in an account. Use idyl profile list to see profiles available to the active identity. Use idyl context use <name> to switch to a different saved account and profile combination. idyl use moves within the active account by entering a Namespace or Workspace.

​
Context

A context is a named CLI configuration. It does not create permissions by itself; it selects an identity, account, profile, Namespace, optional Workspace, and Subnet for commands. Commands can override context values with flags such as --account-id, --profile, --namespace, --workspace, and --subnet.

​
Namespace, Workspace, and Subnet selection

Namespace and subnet answer different questions: Set saved values when most commands should use the same target:
Enter a Namespace for direct Workload commands, or a Workspace within it for Workspace-local file and Run commands:
Entering a bare Namespace clears the entered Workspace. It does not delete the Workspace or change direct Workloads. Use command flags when one command should use a different target.