[MINIFICPP-1223] Stop reloading script files every time ExecutePythonProcessor is triggered

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.0.0, 0.12.0
• Assignee: Gábor Gyimesi
• Reporter: Adam Hunyadi
• Created: 13/May/20 13:24
• Updated: 03/Jan/22 09:37
• Resolved: 03/Jan/22 09:27

Description

Acceptance criteria:

GIVEN A Getfile -> ExecutePythonScript (with "Reload on Script Change" not set) -> Putfile workflow
WHEN The ExecutePythonScript is run twice with an update on the script file inbetween
THEN On the second execution the behaviour of the ExecuteScriptProcessor should not change

GIVEN A Getfile -> ExecutePythonScript (with "Reload on Script Change" disabled) -> Putfile workflow
WHEN The ExecutePythonScript is run twice with an update on the script file inbetween
THEN On the second execution the behaviour of the ExecuteScriptProcessor should not change

GIVEN A Getfile -> ExecutePythonScript (with "Reload on Script Change" enabled) -> Putfile workflow
WHEN The ExecutePythonScript is run twice with an update on the script file inbetween
THEN On the second execution the behaviour of the ExecuteScriptProcessor should follow the updated script

Background:
For backward compatibility, we went for keeping the behaviour of reading the script file every time the processor is triggered intact.

Proposal:

We would like to add an option called "Reload on Script Change" to toggle this with the first major release.

Issue Links

• is related to: MINIFICPP-1240 Check last modified timestamp of the inode before re-reading the script file of ExecutePythonScript