search

BigBoot / AutoKuma

AutoKuma is a utility that automates the creation of Uptime Kuma monitors based on Docker container labels. With AutoKuma, you can eliminate the need for manual monitor creation in the Uptime Kuma UI.
MIT License
186 stars 14 forks source link

static checks should support recursive dirs #28

Open johntdyer opened 4 months ago

johntdyer commented 4 months ago

I might want to organize my static checks in folders but the feature currently doesnt support recursive search into folders. This would be a nice thing to have

johntdyer commented 4 months ago

FWIW I now get this error, which I think is new for 0.6.0

WARN [autokuma::sync] Encountered error during sync: Unable to deserialize: Unsupported static monitor file type: /static/adsb, supported: .json, .toml
WARN [autokuma::sync] Encountered error during sync: Unable to deserialize: Unsupported static monitor file type: /static/adsb, supported: .json, .toml
WARN [autokuma::sync] Encountered error during sync: Unable to deserialize: Unsupported static monitor file type: /static/adsb, supported: .json, .toml
WARN [autokuma::sync] Encountered error during sync: Unable to deserialize: Unsupported static monitor file type: /static/adsb, supported: .json, .toml
WARN [autokuma::sync] Encountered error during sync: Unable to deserialize: Unsupported static monitor file type: /static/adsb, supported: .json, .toml
WARN [autokuma::sync] Encountered error during sync: Unable to deserialize: Unsupported static monitor file type: /static/adsb, supported: .json, .toml
BigBoot commented 4 months ago

Yes, static monitors still do not support recursive search, I'm hesitant to add this because the filename is used as the id and i'm not sure something like <dir>/<filename> would be a good fit for the id