clarify 'metadata.mtime' usage and shortcomings (#2307)

pull/2396/head
Mike Fährmann 3 years ago
parent bfa5e61900
commit acbb0f5a57
No known key found for this signature in database
GPG Key ID: 5680CA389D365A88

@ -1980,7 +1980,7 @@ Description
extractor.skeb.sent-requests extractor.skeb.sent-requests
------------------------- ----------------------------
Type Type
``bool`` ``bool``
Default Default
@ -3128,6 +3128,16 @@ Description
Set modification times for generated metadata files Set modification times for generated metadata files
according to the accompanying downloaded file. according to the accompanying downloaded file.
Enabling this option will only have an effect
*if* there is actual ``mtime`` metadata available, that is
* after a file download (``"event": "file"`` (default), ``"event": "after"``)
* when running *after* an ``mtime`` post processes for the same `event <metadata.event_>`__
For example, a ``metadata`` post processor for ``"event": "post"`` will
*not* be able to set its file's modification time unless an ``mtime``
post processor with ``"event": "post"`` runs *before* it.
mtime.event mtime.event
----------- -----------

Loading…
Cancel
Save