[FEATURE] Switch a service from scheduler method to ui method (avoid manually edit it in DB)

[thelittlefireman]

What's needed and why?

Hi,

I would like to drop a huge part of my docker-compose environments variables to get a more clean and unify configuration with the UI.
I delete these env vars and restart bw-scheduler, but in DB the still be marked as setup with scheduler

I've deleted an BBB service from environment variable in my docker compose file, but it is still present in the bw-scheduler/ui, and I can't delete it because it's marked as setup with scheduler (no dustbin icon). Moreover, it creates some wrong configuration cause the FQDN associated with it doesn't exist anymore (let'encrypt can't renew issue).

I prefer to avoid to directly edit the DB by changing the method column on every row. (method db)
Could it be possible to have a button to switch a service from scheduler to ui ?
Thanks

Implementations ideas (optional)

Maybe a button to switch a service from manage by scheduer to ui.

Code of Conduct

• I agree to follow this project's Code of Conduct

[TheophileDiot]

Hi @thelittlefireman, thank you for opening this issue. I guess this can also be recognized as a bug.
I'll have a look at an elegant way of doing so and let you know of my findings.

[TheophileDiot]

@thelittlefireman did you try to do a down and up ? A simple restart doesn't change the containers metadata like the env or labels.

[TheophileDiot]

@thelittlefireman bump

[thelittlefireman]

Sorry I was busy these weeks, I try what you suggest, and recreater container, that's working but that break everything and just wipe out all my configuration...

I will try to revert by adding back my conf, manualy edit the DB to change the 'method ' colum and then re-remove all variables.

[TheophileDiot]

If it wipes your whole configuration it means that you are not saving it properly using volumes @thelittlefireman

Have a look at our examples and the documentation about it.

[thelittlefireman]

Nop i got properly mounted volumes. it just wipe thé settings that was setup as environnements variables. I will roll back with a database backup.

[TheophileDiot]

Hi @thelittlefireman, turns out it was a bug in the 1.6.0-rc3version, which is now fixed in the 1.6.0-rc4