lennybot
Usage
GitHub Actions
- uses: raynigon/lennybot@v1.0.0
env:
LB_CONFIG_FILE: ".github/lennybot.yaml"
LB_GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
CLI
Install package with pip install lennybot.
To start the application run the lennybot command.
You can specify the Action which should be executed.
This action can be "ci", "plan" or "apply".
The CI CLI action executed apply and handles git operations such as, commit and branch creation.
The plan action allows to plan updates and save the plan for later.
The apply action can either execute an existing plan, or create a new plan and apply it immediately.
Docker
To run the lennybot as docker image execute:
docker run --rm -v "$(pwd):/workspace/ raynigon/lennybot
How it works
The lennybot allows to define multiple applications. Each application has to have a version source, which can be queried to determine the latest version. If a newer version is available, the lennybot executes multiple pre defined actions per application. E.g. Update Docker Image Tags. Sometimes there are conditions which need to be fulfilled before the action can be executed. These conditions can be specified as checks. E.g. Check if the docker image is available in the registry, because sometimes a new version of an applications gets released, but the docker image is not available yet.
The applications, sources, checks and actions can be configured in the config.yml file.
For more information see below.
Configuration
The lennybot can be configured via the config.yml file and environment variables.
If the config.yml file is not in the root of the current working directory, the LB_CONFIG_FILEenvironment variable can be used to pass the location of the configuration file to the lennybot.
The configuration file has multiple top level objects. Each section represents a configuration object.
State
| Path | Description |
|---|---|
| state.file | The state file which is used to store the version of each application |
GitHub
| Path | Description |
|---|---|
| state.pr.enabled | Toggle PR creation in CI mode. Has to be either true or false |
| state.pr.repository | The name of the repository in github on which the PR should be created |
| state.pr.branchPrefix | Prefix for the branch name which should be used to create the PRs |
Applications
| Property | Description |
|---|---|
| applications[*].name | The name of the application which should be updated |
| applications[*].source | The configuration for the source of the latest version. This is specific to the type of source, see below for the diffrent source types. |
| applications[*].actions[*].type | The action has to be one of these types "image-tag-update", "download-resources" or "update-yaml". See below for details. |
| applications[*].actions[*].url | |
| applications[*].actions[*].target | |
| applications[*].actions[*].image | |
| applications[*].actions[*].kustomizePath | |
| applications[*].actions[*].tagPattern | |
| applications[*].actions[*].targetFile | |
| applications[*].actions[*].yamlPath | |
| applications[*].actions[*].valuePattern |
Sources
GitHub Source
| Property | Description |
|---|---|
| .type | The source has to be either of the type "github" or of the type "github-query". See below for details. |
| .repository | The GitHub Repository which should be used to determine the latest version |
| .regex | The regex pattern which is used to extract the semver version code from the tag value |
GitHub Query Source
| Property | Description |
|---|---|
| .type | The source has to be either of the type "github" or of the type "github-query". See below for details. |
| .repository | The GitHub Repository which should be used to determine the latest version |
| .regex | The regex pattern which is used to extract the semver version code from the tag value |
Checks
Actions
Image Tag Update Action
| Property | Description |
|---|---|
| .type | The action has to be one of these types "image-tag-update", "download-resources" or "update-yaml". See below for details. |
| .url | |
| .target | |
| .image | |
| .kustomizePath | |
| .tagPattern | |
| .targetFile | |
| .yamlPath | |
| .valuePattern |
Download Resource Action
Update YAML Action
Update JSON Action
Update Dockerfile Action
Origin
Once upon time a colleague (Lenny) left my team. Besides being an Apache Solr genius, one of the tasks he really liked doing, was the updating of the dependencies in our applications. Since everyone else in the team didnt like this job, we needed some automation for this. The lennybot was born to replace our colleague. Since then the lennybot evolved and finally got replaced by the dependabot. Some years later i needed a solution to upgrade components managed with kustomize. This lead to the creation of a new lennybot which is able to automatically search for updates and upgrades the resources with their latest versions.
1 maintainer
Metadata
1 maintainer
Release files for lennybot 1.0.33
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lennybot-1.0.33.tar.gz | 26.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lennybot-1.0.33-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 58.6 kB
Release files / lennybot-1.0.33.tar.gz
| Download URL | lennybot-1.0.33.tar.gz |
|---|---|
| Size | 26.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a1c662071bc439231e9e1cd67bf8a8501b582da7551bcf69f804da0e891b3604
|
|
BLAKE2b-256 checksum How to use checksums |
c8fe9671c6e29fff1efe4b0b62545539e714f2215e3f0bf291491f29e2059ee4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / lennybot-1.0.33-py3-none-any.whl
| Download URL | lennybot-1.0.33-py3-none-any.whl |
|---|---|
| Size | 32.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f71f38eaffdf6171925676604fa3dd85dab34853874701622151180634ec700
|
|
BLAKE2b-256 checksum How to use checksums |
744870a6827bdde6340acaa5038d409c3dacd963a286d2ba3fa2d58559f20d45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
