Title: What if Dependabot and Ansible had a child? 
Well for me that could be Updatecli.<p>Updatecli is a project that I started to help maintain the infrastructure of the Jenkins project. I needed something flexible enough to update YAML with whatever information needed. Because let’s say it, everybody loves YAML. YAML is everywhere.<p>Run it from everywhere…<p>Updatecli is a command-line tool written in Golang and available for Windows, Linux, MacOSx, amd64, arm64, thank you Goreleaser
All of that to say that it runs from wherever CI or laptop we need.<p>As of today, Updatecli opened over 3000 Pull requests on Github, and it evolved to update automatically Dockerfile, Markdown, Helm Chart, and of course a lot of YAML for tools like Puppet, Kubernetes, or Jenkins.<p>How does it work?<p>Updatecli loads pipeline configurations from YAML(s) or Golang templates then enforce the state defined by the pipeline configuration.
A pipeline run as followed:<p>1. Clone in a temporary location any git repositories used by the pipeline.<p>2. Fetch information for every *source* defined, and then inject them as entry parameters into condition(s) and target(s).<p>3. Test that all *conditions* defined succeed otherwise abort the pipeline.<p>4. Enforce the state for every *target* defined. A state means different things depending on the resource type, more on this later.<p>5. Commit and open pull requests when needed.<p>6. Apply next pipeline<p>A Updatecli pipeline relies on resources aka “extension” aka “plugins” to adapt pipeline behavior. By combining them, we can easily automate scenarios for release workflow, GitOps, dependency management, documentation update, etc.<p>A simple scenario could be:
* Retrieve the latest Golang version
* Test that a docker image with the latest Golang version exist on Dockerhub
* If it exists, then bump the version in a YAML file and open a pull request on GitHub with the change<p>As of today, there are 9 extensions for &quot;sources&quot;, 8 for &quot;conditions&quot;, 6 for &quot;targets&quot;, 2 for git repositories, and 1 for pull requests.<p>A very simple pipeline is available on 
-&gt; <a href="https:&#x2F;&#x2F;www.updatecli.io&#x2F;docs&#x2F;prologue&#x2F;quick-start&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.updatecli.io&#x2F;docs&#x2F;prologue&#x2F;quick-start&#x2F;</a><p>For more complex pipelines, you can look for directories named “updatecli&#x2F;updatecli.d” at the root of repositories on <a href="https:&#x2F;&#x2F;github.com&#x2F;updatecli" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;updatecli</a> or the Jenkins infrastructure repository such as  
<a href="https:&#x2F;&#x2F;github.com&#x2F;jenkins-infra&#x2F;kubernetes-management&#x2F;tree&#x2F;main&#x2F;updatecli" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;jenkins-infra&#x2F;kubernetes-management&#x2F;tree&#x2F;...</a><p>I maintain a documentation website to document the different configuration.
It’s not perfect but it’s available on www.updatecli.io<p>What’s next?<p>Well, it depends on many things. Updatecli is since the beginning, a fun side project, I wanted to practice Golang programming while automating tedious recurring tasks. I built it in a way that I could reuse it across the different projects which I maintain. It’s rather simple to add new resources so I’ll keep adding them based on my needs, I welcome any contributions that would benefit the community.<p>More information on
<a href="https:&#x2F;&#x2F;www.updatecli.io" rel="nofollow">https:&#x2F;&#x2F;www.updatecli.io</a>
<a href="https:&#x2F;&#x2F;github.com&#x2F;updatecli&#x2F;updatecli" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;updatecli&#x2F;updatecli</a>
Upvote: