Skip to content

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 03 May 20:24
· 32 commits to main since this release
4668dd0

Breaking change

When switching context inside an active kubert shell, kubert now defaults to update the context in-place instead of spawning a new nested sub-shell on every kubert ctx call. $SHLVL no longer grows on each switch.

You can likely ignore this change, specifically safe to ignore if:

  • you don't depend on a new (nested) sub-shell being spawned on every context switch
    • e.g. relying on shell exit to automatically revert to a previous context
  • you don't use KUBERT_SHELL_CONTEXT or KUBERT_SHELL_ORIGINAL_KUBECONFIG in the kubert sub-shell (to use these now, you need to configure shell-init, more on that here)

This change does not break context isolation. Each kubert shell still gets its own isolated temporary kubeconfig. On an in-place switch, kubert atomically rewrites that file's contents.

To restore the previous behavior and get nested sub-shells, pass --nested to kubert ctx or set nested: true in your config.

For full details, check docs/ctx-shell-modes.md

Changelog

Breaking changes

  • c4d8140: feat(ctx)!: switch context in-place when already inside a kubert shell (#64) (@idebeijer)

Bug fixes

  • fc88a26: fix(hooks): expose KUBERT_SHELL_CONTEXT and KUBERT_SHELL_ORIGINAL_KUBECONFIG to all hook invocations (@idebeijer)
  • 5b2f457: fix: clean up temp files on chmod and rename failures (@idebeijer)

Documentation

Others

Full Changelog: v0.7.1...v0.8.0