Update ghcr.io/moghtech/komodo-periphery Docker tag to v1.19.4 #50
Reference in New Issue
Block a user
Delete Branch "refs/pull/50/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.18.4->1.19.4Release Notes
moghtech/komodo (ghcr.io/moghtech/komodo-periphery)
v1.19.4: Komodo v1.19.4Compare Source
Changelog
Resource
UI
Misc
peripheryandkmbinary size by ~5 MB using cargo stripdisable_non_admin_createon tag creationv1.19.3: Komodo v1.19.3Compare Source
Changelog
This is a small release fixing various bugs, including the longstanding issue #427. It also includes a change to the Resource Sync UI, improving the look and saving users an extra click.
Resources
BuildReposuccess.Misc
v1.19.2: Komodo v1.19.2Compare Source
🚨 Updating from v1.18.X or under? Review https://komo.do/docs/resources/auto-update for changes to "Poll for Updates" and "Auto Update" features.
Changelog
Resource
Misc
urlencodedatabase credentials to ensure they reach database correctlyx-token-auth:<ACCESS_TOKEN>(see screenshot). This works for any other custom value you need in the<username>:part of basic authentication. If not included, will default to usetoken:<ACCESS_TOKEN>as before.v1.19.1: Komodo v1.19.1Compare Source
Changelog
🚨 In order to use
config_files, Periphery should also be updated to v1.19.1❗️In addition to
ghcr.io, images are now also being published tomoghtech/komodo-*(Docker Hub)Stack
config_files🦎One of the most common requests was to allow in UI editing of
.envfiles on server / in repo. But really, there's not much difference between.envfiles and any config file which a Stack may be dependent on.This release adds the ability to configure all config files Stacks depend on, such as json / yaml app config files, and edit the files from the Komodo UI. Just add the relative path to the files (from the Run Directory) to the Stack "Config Files".
Users which are already using "Additional Env File" feature will find, with no change, that they can now see / edit all their additional env files from the UI. The only difference is that "Additional Env Files" will also be included in the
docker compose upcommand (with --env-file flag), while "Config Files" will not.The UI editors support syntax highlighting for a couple of common formats, such as toml, yaml, json, ini, and shell / .env. It will be challenging to add support for all the various formats used, so I won't personally accept requests to add more. The support is set up for extension though, please raise a PR adding support for additional syntax highlighting you would like and I am happy to review and merge it.
Deploy Stack If Changed 🦎
The biggest issue with Deploy Stack If Changed up to v1.19.1 was that it would only Redeploy if one of the compose files changed. If the commit is only to config file, these changes would be missed.
Now in v1.19.1, "Config Files" and "Additional Env Files" will also be tracked and diffed for changes. This means changes made only to a config / additional env file can also trigger deploy using Deploy Stack If Changed.
Any change made to a compose file or additional env file will always lead to a full Redeploy. However users are able to configure what kind of behavior diffs to config files leads to, either globally for the Stack or at the service level. For example, you can set diffs in a config file to only restart a specific service or services.
Action Example 🦎
If you configure Stacks with all dependent
config_files, you can create an Action like this:It is re-usable in multiple Procedures, which can wrap the Action an hardcode the actual Repo.
You then setup webhooks for the Procedure on push, or can schedule the Procedure to run at polling intervals.
Community Contributions 🦎
This last week saw a ton of end-to-end feature development in community contributions, and I wanted to highlight them here:
executeAPI -- RunStackService -- in #732 by @bpbradleydocker compose runResource
moghtech/komodo-*(docker.io)Misc
executeAPI -- SendAlertv1.19.0: Komodo v1.19.0Compare Source
/repo-cachemount from Core compose service -- it's not needed, and only causes problems.- <host path>/komodo/backups:/backupsto Core compose service. https://komo.do/docs/setup/backupChangelog
The
kmCLI 🦎Introducing
km, the new CLI for Komodo.Some examples:
km --helpkm ps --downkm inspect my-containerkm ls --tag networkkm deploy stack my-stackkm run action my-action -ykm set var MY_VAR my_value -ykm update build my-build "version=1.19.0&branch=release"km x commit my-syncIt also implements some operational features using direct database connection:
km database backupkm db restorekm db copy- Replaces theghcr.io/moghtech/komodo-utilimagekm set user mbecks super-admin truekm set user mbecks password "temp-password"You can either install it using the published binaries and a similar install script to Periphery systemd (but simpler, no systemd involved), as well as Homebrew for MacOS. A distroless image containing the binary is published at
ghcr.io/moghtech/komodo-cli.Action Arguments 🦎
This PR also Implement the Action Arguments feature re #149
ARGSobject in Action scripts.RunActionkm run action my-action "arg1=value1&arg2=value2"ARGS.WEBHOOK_BRANCHandARGS.WEBHOOK_BODYrespectively.Resource
UI
KOMODO_ENABLE_FANCY_TOML=trueto use the previous onelocal_authis enabled, Admins can now create new local users from the UI, even whendisable_user_registration = true.Misc
allowed_ipsnow support Ipv4/6 subnets (like172.16.0.0/16) by @bpbradley in #666Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.