-
|
The x-th attempt to get into UpdateCLI. So far, it hasn't grown on me mainly because the whole autodiscovery always tries to do too much or doesn't give me the results I want.
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 7 replies
-
I only use the default I always use Updatecli with manifests to automate git repository update. With Updatecli you need to specify manifest. Regarding autodiscovery plugin, it's also possible to restrict or ignore some dependencies Here is an example: https://github.com/epinio/helm-charts/blob/main/updatecli/updatecli.d/autodiscovery/default.yaml Every autodiscovery plugin comes with ignore/only rules
Right now, It's not possible to disable changelogs, but we could easily provide a cli flag to ignore changelogs When you start writing Updatecli manifest, I highly recommand you to write them from a IDE that support jsonschema store such as Intellij, Vscode, or Neovim (with the write plugin) |
Beta Was this translation helpful? Give feedback.
-
|
How do you configure the autodiscovery? |
Beta Was this translation helpful? Give feedback.
-
|
Interesting feedback, in your case with an empty If you execute If you execute So for example the following file: It would be the equivalent of running the following commands:
But in your case, with the file: it's apparently doing Instead, you could use the updatecli-compose.yaml file and then run Or The updatecli compose file is not mandatory, in fact It came years after Updatecli was created.
Where in this case the weekly file is only triggered when a new Updatecli version is released as it's responsible to automatically publish Updatecli release note to the Updatecli website https://www.updatecli.io/changelogs/updatecli/ |
Beta Was this translation helpful? Give feedback.
Interesting feedback, in your case with an empty
updatecli-compose.yaml, I would consider this as a UX bug because:If you execute
updatecli diff/apply, without--config, Updatecli automatically loads manifests detected fromupdatecli.yamlandupdatecli.d/*but if it can't find one then it fallbacks to all autodiscovery plugins without git integration which is useless unless you want to see the kind of update you can automatically do.If you execute
updatecli compose diff/apply, without--filethen it tries to detect manifest fromupdatecli-compose.yamlupdatecli compose diff/applyis a wrapper aroundupdatecli diff/applywhere each policy entry is a different Updatecli executionSo for e…