Olivier Vernin
Olivier Vernin
> I fear retrieving and storing the original value to generate this URL won't be that easy, AFAIU it's never stored anywhere. It won't be trivial but necessary, I have...
For the same of this feature, I am hesitating between `auto`, `generic`, `builder` which explain why those three names are used in the pullrequest.
Please also note that this PR doesn't generate "pipelines" but "pipeline manifest"
The auto-discovery feature introduced in this pullrequest , means it should be possible to run updatecli commands without providing any manifest as `updatecli diff` could discovery available pipeline. But due...
I think it would be better to split this pullrequest in two. One about the autodiscovery and a second one about helm chart dependency update
Here is the documentation that I started on the autodiscovery feature https://github.com/updatecli/website/pull/428
After additional experimenting, I am starting to wonder when to enable the "local" discovery. What I mean by "local" autodiscovery is when updatecli tries to identify potential pipeline based on...
I added manifest examples in `e2e/updatecli.d/warning.d/autodiscovery`
so I found the local autodiscovery quite annoying by default, so I disable it by default
I am just dropping this repository https://github.com/rancher/fleet-examples To remind myself to use it in my test