Previously these values would be persisted to a local edn file which by default lives at config/mutable.edn. However, in modern cloud environments this is not durable. For example when running Yetibot on Kubernetes this would be lost on each pod creation (unless a durable disk was mounted, but that's an unnecessary complication). We already have a durable place to store keys and values: the Postgres database.

All of these use cases will now move to a single yetibot_channels table.

What does this mean for me?

Given that mutable config hasn't been heavily used the migration should be quite painless. We are not providing an automated migration tool, so your options are:

Do nothing if you're not using any mutable config yet (quite likely) 😅

Use Yetibot to recreate the config, e.g. channel set jia-project myjira

Look in config/mutable.edn and manually copy the key/values and chat source rooms to the yetibot_channels Postgres table. For example, if your mutable.edn looks like: