google / kasane Goto Github PK

Kasane should bundle the helpers lib and add it to the search path automatically.

It would be useful to load an existing k8s object from the cluster or at least check its presence. It raises the question of where to store such an object, though, as it can't be directly loaded into the layers without issues. Migrate env to context and allow dynamic context?

To make kasane into a full-featured manager it needs to support object removal. That could be a trivial extension of layers for use cases when there are dynamically created objects.

Can define a global env named mode:

• apply is the current kasane apply action
• remove would allow to add additional objects to be removed with when: mode == 'remove' (also see #10)
• purge would do the remove plus more (e.g. remove all the relevant CRDs)

e.g. if pwgen and pki management were integrated into kasane it could be a complete replacement for stash deployments.

As uncovered in #13, it'd be nice to have a version command to report the current kasane version.

Now that 0.1.3 won't crash if highlight isn't installed it's time to find a better highlighting strategy other than forking to nodejs app.

Pygments can't highlight yaml in any meaningful way, though. See also https://bitbucket.org/birkenfeld/pygments-main/issues/890/yaml-highlight and https://bitbucket.org/birkenfeld/pygments-main/pull-requests/762/improving-lexing-of-yaml-mappings/diff

and all the flags

As Kasanefiles grow longer they start to become a mess. Add some way to group several layers via an include: or block: option like ansible does that.

One question here is if jsonnet layers should be block scoped and I have a tentative answer of yes.

It'd be helpful if kasane could one-click install apps via

kasane apply http://example.com/Kasanefile

This can be done by extending the -p flag to point at Kasanefiles and adding support for remote projects.

Many exceptions are thrown and never caught resulting in subpar user experience.