You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes major changes to channels are made on cloned channels, preserving their previous version in a disabled state, with the goal of switching back to them in case of problems (rollback).
The whole concept would be ok if we could get rid of those backup channels after a few days or weeks.
That's not always the case, since a few customers like to keep a very large attic of obsolete objects, with the result of having up to 70% of disabled channels.
I wrote a bash script that, using channels' statuses fetched from here /api/channels/statuses?includeUndeployed=false deletes channels from the local mirthsync'd target dir (see attachment).
Now, it works, but it would be certainly more elegant and efficient to have an option switch into mirthsync.
I'd like to provide a patch, but I literally have got no time left to learn another language such as Clojure.
Sometimes major changes to channels are made on cloned channels, preserving their previous version in a disabled state, with the goal of switching back to them in case of problems (rollback).
The whole concept would be ok if we could get rid of those backup channels after a few days or weeks.
That's not always the case, since a few customers like to keep a very large attic of obsolete objects, with the result of having up to 70% of disabled channels.
I wrote a bash script that, using channels' statuses fetched from here
/api/channels/statuses?includeUndeployed=false
deletes channels from the local mirthsync'd target dir (see attachment).Now, it works, but it would be certainly more elegant and efficient to have an option switch into mirthsync.
I'd like to provide a patch, but I literally have got no time left to learn another language such as Clojure.
Script:
I had to rename it to .txt in order to upload it.
mirth_purge_disabled.sh.txt
It's a post processing script, but I realize now it would be more practical if it were a wrapper to mirthsync.sh
Update: probably related to these #45, #26, #34
The text was updated successfully, but these errors were encountered: