Concepts
tsm keeps your connections in one personal configuration file. Five terms describe them:
| Concept | What it is | Example |
|---|---|---|
| Project | A group of related environments | tsm |
| Environment | One tSM installation, identified by its URL | dev, test |
| Account | Your credentials for one environment (API key, username/password or token) | personal |
| Context | Environment + account + tenant: where and as whom a command runs | dev |
| Workspace | A Git checkout of a project registered under a name | demo |
Credentials are stored in the operating system's credential store, never in the configuration file.
Which context is used
--context NAMEon the command line,- otherwise the default context of the current workspace,
- otherwise the global default set by
tsm context use NAME --global.
tsm context show --explain prints the selected context and why it was chosen.
Workspaces
A workspace is selected by --workspace NAME|PATH, or by the current directory (the nearest registered parent).
There is no globally active workspace. A context never changes the checkout: switching --context
only changes where commands send requests.
tsm-project.yaml in the checkout is shared in Git and holds only project/product/packages/components.
Personal connections, paths and credentials do not belong there.
In the experimental CLI build, a workspace can also run its own local tSM instance; see Local runtime.