[Bug?][Feature request?] postprocessors.metadata firing when set to POST even without --write-metadata flag

[Scripter17]

I set postprocessors.metadata to fire on post as per this comment and while it does work, shouldn't it only fire when --write-metadata is used?

If it is supposed to without the flag, then maybe allowing a "condition":"--write-metadata" in postprocessor configs would be worthwhile
This could also allow for pseduo-user defined command line flags by not limiting it to existing flags

[mikf]

shouldn't it only fire when --write-metadata is used?

Probably, but that's not how the current post processing system works. --write-metadata only adds another metadata post processor to the list (it's possible to have more than one active at a time). There is no way to enable/disable a post processor set in a config file with a command-line switch.

What you can do is create a second config file with only the metadata post processor in it and load it with -c when you want it enabled.

[mikf]

83fc4c1 and 6ecb710 should somewhat improve the post processor situation.

These make it possible to globally define your own post processors and run them with -P/--postprocessor and to overwrite the settings for the "default" post processors used by flags like --write-metadata.

I have no idea how and where to document this, though.

then maybe allowing a "condition":"--write-metadata" in postprocessor configs would be worthwhile

#1460 and 3cbbefd