Olivier Vernin

I propose to target v0.33.0 (totally arbitrary version) to move this from experimental to GA :) I already assign this issue to that milestone so we don't forget

> > if it wouldn't be better to switch Apache2. > > Any specific arguments against MIT or in favor of Apache 2? > > > more restrictive licenses model...

> shrug https://www.exygy.com/blog/which-license-should-i-use-mit-vs-apache-vs-gpl I think the "you are afraid of no one using your code, but you are also afraid of legal ambiguity and patent trolls" resume very well my...

> I didn't managed to reproduce e2e errors locally. https://github.com/updatecli/updatecli/runs/6985093474?check_suite_focus=true : > > ``` > $ ./dist/updatecli diff --config e2e/updatecli.d/success.d/yaml --values e2e/values.yaml > [...] > Run Summary > =========== >...

I am spotting several errors ``` ⚠ Key 'name', from file 'e2e/updatecli.d/success.d/yamlExample.yaml', was updated from 'Test yaml resource' to 'Test yaml resource change' ERROR: something went wrong in target "testFilesSourceInput"...

The e2e yamlfile that I put to test the PR, are wrong ```e2e/updatecli.d/success.d/yamlExample*yaml```

So the last pipeline that need to work is `updatecli.d/success.d/yaml-files.yaml` The purpose is to be sure that `make test-e2e` works from the root of the repository

As far as I remember the E2E tests need to be fixed

Well the recent change that I did in yaml source broke you PR ``` SOURCES ======= fromUrl ------- ERROR: ✗ the yaml file "/home/olblak/Projects/Updatecli/updatecli/https:/raw.githubusercontent.com/updatecli/updatecli/dc90759914718beee17101c693911088cfbf6deb/examples/values.yaml" does not exist fromExplicitFile ---------------- ERROR:...

> Well the recent change that I did in yaml source broke you PR > > ``` > SOURCES > ======= > > fromUrl > ------- > ERROR: ✗ the...