kubepile 0.0.4 → 0.0.5

package/README.md

@@ -36,6 +36,15 @@ Kubepile will never set a `current-context`, out of the design belief that
 npm install -g kubepile
 ```
 
+Kubepile also includes a small shell helper that you need to install once:
+
+```sh
+kubepile install
+```
+
+Once you've installed the shell helper, either start a new shell or re-source
+your `.zshrc`/`.bashrc`/`.profile`/etc. Kubepile supports Zsh, Bash, and Fish.
+
 ## Compile
 
 ```sh
@@ -65,28 +74,35 @@ Running `kubepile` with no command prints help.
 
 ## Source
 
-`kubepile source <context>` switches your current shell to one context by
-creating a temporary kubeconfig containing only that context and exporting
-`KUBECONFIG` to point at it. It also prefixes your shell prompt with the context
-name.
+`kubepile source <context>` switches your current shell to use a specific
+Kubernetes context by default by creating a temporary kubeconfig with that
+context set as the current-context, and exporting `KUBECONFIG` to point at it.
+It also prefixes your shell prompt with the context name.
 
-Shells do not let child processes modify the parent shell environment, so this
-requires installing a small shell function first:
+```sh
+kubepile source prod
+# Your shell prompt is now:
+# (prod) WHATEVER_YOUR_OLD_PROMPT_WAS
+# All kubectl commands will use the prod context
+```
+
+To switch to a different context, just run the `source` command with a new
+context:
 
 ```sh
-kubepile install
+kubepile source dev
 ```
 
-Then start a new shell and run:
+Note that this requires installing the shell helpers listed in the
+installation instructions. If you haven't installed them yet, install them
+with:
 
 ```sh
-kubepile source prod
+kubepile install
 ```
 
-`kubepile install` installs only for your current shell. It supports bash, zsh,
-and fish. The installed function proxies every normal command to the real
-`kubepile` binary with `command kubepile`, so it follows whatever `kubepile` is
-currently on your `PATH` after tools like `nvm` update it.
+And re-source your main shell config (such as e.g. a `.zshrc`) or start a new
+shell.
 
 ## Split
 

package/dist/package.json

@@ -1,6 +1,6 @@
 {
     "name": "kubepile",
-    "version": "0.0.4",
+    "version": "0.0.5",
     "description": "Compile and split kubeconfig files from ~/.config/kubepile.",
     "type": "module",
     "main": "./dist/src/kubepile.js",

package/dist/src/shell.js

@@ -1,16 +1,22 @@
 import { mkdir, mkdtemp, readFile, writeFile } from "node:fs/promises";
 import os from "node:os";
 import path from "node:path";
-import { defaultKubeConfigPath, extractContextConfig, readKubeConfigFile, serializeKubeConfig, } from "./kubepile.js";
+import { defaultKubeConfigPath, readKubeConfigFile, serializeKubeConfig, } from "./kubepile.js";
 const SHELL_BLOCK_START = "# >>> kubepile shell integration >>>";
 const SHELL_BLOCK_END = "# <<< kubepile shell integration <<<";
 export async function generateShellCommand(contextName, options = {}) {
     const sourcePath = options.sourcePath ?? defaultKubeConfigPath();
     const shell = options.shell ?? "posix";
     const sourceConfig = await readKubeConfigFile(sourcePath);
-    const contextConfig = extractContextConfig(sourceConfig, contextName, sourcePath);
+    const contextConfig = {
+        ...sourceConfig,
+        "current-context": contextName,
+    };
     const tempRoot = await mkdtemp(path.join(options.tempDir ?? os.tmpdir(), "kubepile-source-"));
     const kubeConfigPath = path.join(tempRoot, "config");
+    if (!sourceConfig.contexts?.some((context) => context.name === contextName)) {
+        throw new Error(`${sourcePath} does not contain context "${contextName}"`);
+    }
     await writeFile(kubeConfigPath, serializeKubeConfig(contextConfig), {
         encoding: "utf8",
         mode: 0o600,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kubepile",
-  "version": "0.0.4",
+  "version": "0.0.5",
   "description": "Compile and split kubeconfig files from ~/.config/kubepile.",
   "type": "module",
   "main": "./dist/src/kubepile.js",