Komodo with Mongo docker deployment in v1.15.0
Closed this issue · 2 comments
My Komodo install went into a restart loop when Watchtower updated it to v1.15.0. It was timing out attempting to connect to the database server which the timeout log reported as localhost:27017 even though I had KOMODO_MONGO_ADDRESS set to mongo:27017. From looking at the updated docs today, it seems that KOMODO_MONGO_* has been renamed to KOMODO_DATABASE_*. This is a reasonable change if the variable is meant to support multiple backing database types, but it is a breaking change that doesn't appear to be called out in the release notes, and I assume there's no compatibility layer to allow the old name(s) to work.
So: was this change intentional? Was there a way to know about it ahead of time or should the release notes be updated, at least? Semver would usually call for a breaking change to be a new major version bump.
I see the change came from 8dbd8fe which appears to have attempted to put aliases in place, but those aliases don't seem to be working.
If 0600276 is the fix for this, can we get that pushed out quickly? :)
Yeah sorry about that, the intention was backwards compatibility, just had to get that patch out.