Adds docs for named profiles#213
Conversation
There was a problem hiding this comment.
Code Review
This pull request introduces named profiles to the Kinetic CLI, enabling users to bundle project, zone, cluster, and namespace configurations under a single name. This feature simplifies switching between infrastructure targets by integrating profiles into the configuration precedence hierarchy (CLI flag > Env var > Profile > Default). The implementation includes a new kinetic profile command group for lifecycle management, atomic JSON storage, and updates to the config show command for improved visibility. I have no feedback to provide.
| # Profiles | ||
|
|
||
| A **profile** bundles the four settings that determine where a Kinetic | ||
| job runs — project, zone, cluster, and namespace — under a single name. |
There was a problem hiding this comment.
Can you link to the configuration page that explains what these all do?
| - You move between projects or namespaces often enough that exporting | ||
| env vars manually is slowing you down. | ||
| - Multiple people share a machine or dotfiles and need clean switching | ||
| between their own configurations. |
There was a problem hiding this comment.
Maybe mention a benefit is being able to utilize spot capacity across regions?
| between their own configurations. | ||
|
|
||
| For single-cluster setups, plain `KINETIC_*` env vars are still the | ||
| simplest path. |
There was a problem hiding this comment.
Maybe link here as well to the config page that shows how to use these env vars?
|
|
||
| ## Storage | ||
|
|
||
| Profiles live in a single JSON file at `~/.kinetic/profiles.json`: |
There was a problem hiding this comment.
Can you mention (here or maybe above in the intro) that profiles are local and per-user and aren't synced across the team?
Depends on PR #212
Adds documentation for named profiles for the kinetic CLI.