Added
- Named profiles, each with its own API key in the OS keyring, so a production key and a sandbox key can live side by side. Pick one per command with
--profile/-p, per shell withLATITUDE_PROFILE, or as the default withlatitude profiles use. Manage them withlatitude profiles create,list,current,show,set,use, andremove.latitude auth login --with-token -p <profile>stores a key in that profile, andlatitude auth statusreports which profile is in use. - A profile can carry a default project (
latitude profiles create <name> --project-slug <slug>). It wins overLATITUDE_PROJECT_SLUGand--global-project-slug;--project-slugstill wins over it.
Notes
- A
LATITUDE_API_KEYset in the shell or in.envstill wins over the default profile andLATITUDE_PROFILE; only-poverrides it. With no profile selected, the CLI behaves as before and keeps using the key stored bylatitude auth login.