Release v0.8.0

Added

• Support for multiple docker hosts, see #62
• Ability to specify custom tls cert when connecting to Uptime Kuma over HTTPS, see #66
• Ability to ignore invalid tls certs when connecting to Uptime Kuma over HTTPS, see #66

Fixed

• Fix control sequences not being expanded in snippets, see #60
• Add missing description property, see #61
• Fix wrong name for query property of database monitors, see #65
• Add missing upside_down property alias, see #71
• Fix possible memory leak, see #41
• Add workaround for ntfy, see #72

Release v0.7.0

Added

• Enable SSL for docker connections (using DOCKER_HOST, DOCKER_CERT_PATH, DOCKER_TLS_VERIFY env vars), see #50
• Create monitors from docker swarm services, see #54
• create_paused property to create new monitors in paused state, see #53

Fixed

• Add missing query property for sqlserver, postgres and mysql, see #36
• Fix parsing of recurring maintenance with no effective date range, see #43
• Filter cyclic parent_name reference, see #56

Changed

• Transparently flatten arrays in static monitor definitions, see #51

Release v0.6.0

Changed

• !! WARNING POTENTIAL BREAKING CHANGE !!: switch from custom templating to Tera
  This change might break your current configuration if one of the following applies:
  • Your labels contain {{, }}, {%, %}, {# or #}:
    Wrap your labels in {% raw %}{% endraw %} to ensure Tera does not try to parse them, e.g.:
    kuma.mygroup.group.name: "This is a {{ Group }}" -> kuma.mygroup.group.name: "{% raw %}This is a {{ Group }}{% endraw %}"
  • You are using Snippets with arguments:
    The syntax for snippet arguments changed from {{@0}}, {{@1}}, {{@2}} etc. to {{args[0]}}, {{args[1]}}, {{args[2]}} etc.
• Static Monitors will be be postprocessed in the same way as monitors defined by container labels, see #33

Fixed

• autokuma: connections not being closed when an error occurs during setup, see #11

Added

• kuma-cli: docker-host management
• kuma-cli: colored output in pretty print mode
• autokuma: add on_delete config option, see #29

Removed

• kuma-cli: toml output format as it's not compatible with all data

Release v0.5.0

Fixed

• Use correct tag name when resolving groups, see #17
• Fix missing snake_case aliases, see #19

Added

• lenient vector parsing for accepted_statuscodes, see #23
• support for push_token, see #21
• Snippets for reduced boilerplate

Release v0.4.1

Added

• Ability to replace template values in tag names (as long as the tags start with the defined prefix), see #14
• Ability to load user-wide AutoKuma config
• log_dir config for storing logs as files

Fixed

• Fixed parsing of max_retries and max_redirects, see #12
• Release pipeline

Changed

• Remove leading slash from container names in template values, see #14
• Added fallback for static_monitors

Release v0.3.2

Added

• Fall back to DOCKER_HOST env variable when no socket_path is specified in AutoKuma docker config
• add docker image for kuma-cli, see #5

Fixed

• exclude parent_name when sending monitor data to server, see #8
• Make parsing of ports more lenient, see #9

Release v0.3.1

Fixed

• Memory leak in kuma-client #1
• Fix documentation for maintenance cli subcommand #4
• Allow deserialization of maintenance timerange without seconds #4

Release v0.3.0

Added

• new CLI client for Uptime Kuma kuma-cli

Changed

• split package into kuma-client and autokuma
• renamed env var AUTOKUMA__KUMA__TAG_NAME to AUTOKUMA__TAG_NAME due to package splitting
• renamed env var AUTOKUMA__KUMA__TAG_COLOR to AUTOKUMA__TAG_COLOR due to package splitting
• renamed env var AUTOKUMA__KUMA__DEFAULT_SETTINGS to AUTOKUMA__DEFAULT_SETTINGS due to package splitting
• automatically append /socket.io/ to KUMA__URL