Alessandro De Maria
Alessandro De Maria
thanks @th31nitiate , issue #443 solves the crash, but highlights the behaviour here explained. The workaround for this new issue is the same as the one I had for #443,...
TBH I looked at it and I don't think you can activate the single mode at all! for JSON to be valid, the file needs to be: ``` { "key":...
Late to the party. @smauermann do you mind joining the #kapitan channel on the kubernetes slack to discuss? Questions: * what secret backend are you using? gkms? * @smauermann for...
BTW even with this patch, with `prune: false` Kapitan crashed quite badly. This PR does not address that issue, which I will re-open in another bug report
The crash is unrelated to this PR. It already exists in the current codebase. Will open another bug report :)
Hello @siku4 , thank you for reporting this issue. I confirm I also observe this behaviour, with the error message being: ``` |reveal function error: targets/XXX/token_private_key file in gkms:targets/XXX/token_private_key_encoded|reveal:targets/XXX/token_private_key does...
From earlier conversation (I proposed/suggested the integration) I think what we want is to evaluate "to be able to process templates written in ytt as a new kapitan input type...
is there an update on this? or a workaround?
@taharah I proposed the same idea some time ago but with a slight variation. ``` parameters: kapitan: compile: - output_path: input_type: jinja | jsonnet | kadet | helm input_paths: -...
Any chance that we could push this at one point?