olblak (8d181e72) at 25 Aug 09:36
chore: Update README license file content
olblak (3e368261) at 25 Aug 09:33
chore: Update README license file content
short description
short description
olblak (71afc75f) at 25 Aug 09:28
chore: Update README license file content
olblak (cbee665f) at 25 Aug 08:54
chore: Update README license file content
\n\nMy suppeor custom body\n\n---\n\n\n\n\n <action id="617fdac1ea28936eec6549341962738e9a16bff676e3f02e53dc7c7c5b1c0afe">\n
1 file(s) updated with "xxxxxxxxxxxxxxxxxxxxxx= Updatecli\n\nlink:https://matrix.to/#/#Updatecli_community:gitter.im[image:https://img.shields.io/matrix/updatecli:matrix.org[]]\nlink:https://github.com/updatecli/updatecli/blob/main/LICENSE[image:https://img.shields.io/github/license/updatecli/updatecli[GitHub]]\nlink:https://goreportcard.com/report/github.com/updatecli/updatecli[image:https://goreportcard.com/badge/github.com/updatecli/updatecli[Go Report Card]]\nlink:https://github.com/updatecli/updatecli/releases[image:https://img.shields.io/github/downloads/updatecli/updatecli/total[GitHub Releases]]\nlink:https://github.com/updatecli/updatecli/releases[image:https://img.shields.io/github/downloads/updatecli/updatecli/latest/total[GitHub Releases]]\nlink:https://img.shields.io/github/actions/workflow/status/updatecli/updatecli/go.yaml?branch=main[image:https://img.shields.io/github/actions/workflow/status/updatecli/updatecli/go.yaml?branch=main[GitHub Workflow Status]]\nlink:https://api.securityscorecards.dev/projects/github.com/updatecli/updatecli[image:https://api.securityscorecards.dev/projects/github.com/updatecli/updatecli/badge[OpenSSF Scorecard]]\nlink:https://bestpractices.coreinfrastructure.org/projects/6731[image:https://bestpractices.coreinfrastructure.org/projects/6731/badge[OpenSSF Best Practices]]\n\n_\"Automatically open a PR on your GitOps repository when a third party service publishes an update\"_\n\nUpdatecli is a tool used to apply file update strategies. Designed to be used from everywhere, each application \"run\" detects if a value needs to be updated using a custom strategy then apply changes according to the strategy.\n\nYou describe your update strategy in a file then you run updatecli to it.\n\nUpdatecli reads a yaml or a go template configuration file, then works into three stages\n\n1. Sources: Based on a rule, updatecli fetches a value that will be injected in later stages such as latest application version.\n2. Conditions: Ensure that conditions are met based on the value retrieved during the source stage.\n3. Targets: Update and publish the target files based on a value retrieved from the source stage.\n\n== Feature\n\n* Flexibility: Easy to define tailored update strategies, you are just one yaml file from it.\n* Portability: Easy to add to your workflow whatever it is. Just one command to run. Of course, it's easy to remove.\n* Extensibility: Easy to add new go packages to support more workflows.\n\n== Why\n\nThere are already many projects out there to continuously update your files, but they all have an opinionated way of doing it and they often want you to adopt a new platform.\nBuilding and distributing software is a difficult task and good practices constantly evolve.\nUpdatecli was built to work independently of the underlying dependencies to update, wherever you need it and combining whatever workflow you are using, as you can see in the following section.\n\n== Demo\n\nlink:https://asciinema.org/a/CR5DIxyTLnvtt8NllEeYAx83U[image:https://asciinema.org/a/CR5DIxyTLnvtt8NllEeYAx83U.svg[Asciinema]]\n\nThe Quick-start is available on link:https://www.updatecli.io/docs/prologue/quick-start/[www.updatecli.io/docs/prologue/quick-start]\n\n== Installation\n\nUpdatecli is a Go binary available for Linux, MacOS and Windows from the link:https://github.com/updatecli/updatecli/releases[release page] or installed via link:https://www.updatecli.io/docs/prologue/installation/[other methods].\n\nVerify File Checksum Signature\n\nInstead of signing all release assets, Updatecli signs the checksums file containing the different release assets checksum.\nYou can download/copy the three files 'checksums.txt.pem', 'checksums.txt.sig', 'checksums.txt' from the latest https://github.com/updatecli/updatecli/releases/latest[release].\nOnce you have the three files locally, you can execute the following command\n\n\\nCOSIGN_EXPERIMENTAL=1 cosign verify-blob --cert checksums.txt.pem --signature checksums.txt.sig checksums.txt\\n
\nA successful output looks like \n\n\\ntlog entry verified with uuid: 73f57e4c16b830ccb615e00814a3481a33365bf48f9bba1c1588886b3344d0ec index: 9085154\\nVerified OK\\n
\n\nNow you can verify the assets checksum integrity.\n\nVerify File Checksum Integrity\n\nBefore verifying the file integrity, you should first verify the checksum file signature.\nOnce you've download both the checksums.txt and your binary, you can verify the integrity of your file by running:\n\\nsha256sum --ignore-missing -c checksums.txt\\n
\n\nVerify Container signature\n\n\\ndocker pull updatecli/updatecli:vx.y.z\\ncosign verify updatecli/updatecli@sha256:<image_digest> \\n
\n== Documentation\n\nThe documentation of Updatecli is available at link:https://www.updatecli.io/docs/prologue/introduction/[www.updatecli.io], but you can also look at the examples
section to get an overview.\n\n=== Example\n\nThis example is copy of the quickstart. You can also find it on link:https://www.updatecli.io/docs/prologue/quick-start/[www.updatecli.io/docs/prologue/quick-start]\n\nWe define an update strategy in \"updatecli.yaml\" then we run updatecli apply --config updatecli.yaml
.\nOur objective is to know if the Jenkins project published a new stable version, if they build an appropriated docker image specifically for jdk11 and automatically update our infrastructure accordingly.\n\n[cols=\"2a,2a\"]\n|===\n|\\n## updatecli.yaml\\ntitle: Update Jenkins Version\\n\\nscms:\\n default:\\n kind: github\\n spec:\\n user: olblak\\n email: me@olblak.com\\n owner: olblak\\n repository: charts\\n token: mySecretTokenWhichShouldNeverUsedThisWay\\n username: olblak\\n branch: main\\n\\nsources:\\n jenkins:\\n name: Get latest Jenkins version\\n kind: jenkins\\n spec:\\n release: weekly\\n\\nconditions:\\n docker:\\n name: \\"Test if Docker Image Published on Registry\\"\\n kind: dockerimage\\n spec:\\n image: jenkins/jenkins\\n architecture: amd64\\n\\ntargets:\\n bumpJenkins:\\n name: jenkins/jenkins docker tag\\n scmID: default\\n kind: yaml\\n spec:\\n file: charts/jenkins/values.yaml\\n key: jenkins.controller.imageTag\\n\\nactions:\\n default:\\n title: Open a GitHub pull request with new Jenkins version\\n kind: github/pullrequest\\n scmID: default\\n target:\\n - bumpJenkins\\n spec:\\n automerge: true\\n mergemethod: squash\\n labels:\\n - dependencies\\n
\n\n|What it says:\n\n. Sources: +\nWhat's the latest jenkins weekly version? +\n=> 2.335 +\n\n. Conditions: +\nIs there a docker image \"jenkins/jenkins\" from Dockerhub with the tag \"2.335\" +\n=> Yes then proceed otherwise abort +\n\n. Targets: +\nDo we have to update the key \"jenkins.controller.imageTag\" from file \"./charts/jenkins/values.yaml\" located on the Github repository olblak/charts to \"2.335\"? +\n=> If yes then execute the action default
opening a GitHub pull request to the \"main\" branch\n\n|===\n\nMore information link:https://www.updatecli.io/docs/prologue/introduction/[here]\n\n\n---\n\n== Contributing\n\nAs a community-oriented project, all contributions are greatly appreciated!\n\nHere is a non-exhaustive list of possible contributions:\n\n*
\n \n Created automatically by <a href="https://www.updatecli.io/">Updatecli\n \nOptions:\n\n Most of Updatecli configuration is done via <a href="https://www.updatecli.io/docs/prologue/quick-start/">its manifest(s). \n
\n Feel free to report any issues at <a href="https://github.com/updatecli/updatecli/issues">github.com/updatecli/updatecli. | \n
olblak (0173d8dc) at 25 Aug 07:53
olblak (f2bd316d) at 25 Aug 07:53
Source:
✔ [license] Retrieve license file content(file)
✔ [readme] Retrieve readme file content(file)
Condition:
✔ [license] Retrieve license file content(file)
✔ [readme] Retrieve license file content(file)
Target:
✔ [license] Update license file content(file)
⚠ [readme] Update README license file content(file)
olblak (0173d8dc) at 13 Mar 12:22
chore: Updated the content of the file "/tmp/updatecli/gitlab/olbla...
install -Dm755 "./updatecli" "${pkgdir}/usr/bin/${pkgname}"
- 'Olivier Vernin <olivier at vernin dot me>'
- 'Jonathan Neidel <aur at jneidel dot com>'
Created by: lemeurherve
return fmt.Errorf("%d target(s) (%s) skipped for %q action", len(skippedTargetIDs), strings.Join(skippedTargetIDs, ","), id)
Created by: lemeurherve
logrus.Errorf("%d target(s) (%s) failed for %q action", len(failedTargetIDs), strings.Join(failedTargetIDs, ","), id)
Created by: lemeurherve
This pull request was automatically created from the [{{ .Filename }}]({{ .FileURL }}) manifest using [Updatecli](https://www.updatecli.io).
This debug message is already displayed in the the gitgeneric library
So if you had the parameter --debug to your command you'll see the message
Created by: dduportal
sourceid: helm1
name: 'Is the 2nd ENV instruction having a "keyword" set to "HELM_VERSION"'
kind: dockerfile
otherwise use the same quoting everywhere instead to be coherent ;)
Why are you returning an error if nothing changed? Wouldn't it be better to return something like
return false, files, message.String(), nil
Created by: lemeurherve
Please report any issues with this tool [here](https://github.com/updatecli/updatecli/issues/new/choose)
Alternatively, link to the issue template chooser. I think linking to issues list is better as users can see existing issues before opening a new one.