BigBoot
BigBoot
The way AutoKuma works just isn't compatible with a 'default for new monitors' kind of setting. AutoKuma generates a desired state and then tries to mutate the existing uptime kuma...
1. i haven't tested an upgrade yet, maybe uptime kuma recreates it's database tables on the 2.0 migration? That would result in a change of ids and therefore AutoKuma losing...
Hi @bnctth, I don't think there's any breaking change, this looks rather like a problem with your labels, let's try to break this down. ``` autokuma-1 | WARN [kuma_client::util] [backups-nasty.toml]...
Sorry I added the `files.follow_symlinks` option and forgot to set a default, should be working now
> Is there plans to support API keys that can be generated from the Uptime Kuma 2.0 UI rather than username/password? There still is no support for API keys on...
This is expected, you can change the sync interval with the `AUTOKUMA__SYNC_INTERVAL`/`sync_interval` (sync interval in seconds) config.
@radokristof Looks like autokuma is unable to parse your list of maintenances I'm not using that feature extensively, but it seems to work here with a bit of testing. FWIW...
Issue should be fixed on the current master
AutoKuma v2 now supports Uptime Kuma v2 by default, as such I'm closing this issue
I've already mentioned this in some other issue but this is a uptime kuma bug. There's basically nothing I can do about this, uptime kuma does not report the id...