Looper does not overwrite pipestat config, should it?

[donaldcampbelljr]

trafficstars

Originally, looper would overwrite the pipestat config upon executing looper run. However, several months ago, we changed it such that it will not overwrite the pipestat config if it finds one already in place.

Running my own pipelines, I've found this behavior confusing and annoying as its led to me changing items in my looper config and then not seeing the changes executed downstream in results reporting. I then must hunt for the location of the pipestat config and delete it before re-running.

I'm contemplating adding the ability to preserve the previous config and create a new one for the current run. This would give us preservation of previous settings for debugging etc and remove the above friction when using looper + pipestat.

Or I may return to having the default behavior be to overwrite the pipestat config. Or perhaps have a flag to toggle such behavior.