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
Describe the bug
An existing v1.x pynonymizer config that has PYNONYMIZER_START_AT='ANONYMIZE_DB'works fine without setting PYNONYMIZER_INPUT. In v2 it looks like INPUT has become mandatory - running v2.x against the same set of env vars that worked with v1.x, I get :
Missing values for required arguments:
Missing INPUT
Missing STRATEGYFILE
To Reproduce
as above
Expected behavior
Feels like INPUT should only be mandatory if the RESTORE_DB step is going to be in play?
Additional context
The text was updated successfully, but these errors were encountered:
simonblake-mp
changed the title
Should INPUTS be mandatory?
Should INPUTS be mandatory when RESTORE_DB is skipped?
Apr 23, 2024
Thank you so much for taking the time to write this up. This change wasnt intentional, I'll take a look at this with the other issues. Watch the patch milestone for updates https://github.com/rwnx/pynonymizer/milestone/4
I've run some tests my side and I think this is because of the changes in #159, rather than a change to behaviour. when using the env vars from 2.2.0 it seems to work.
Describe the bug
An existing v1.x pynonymizer config that has
PYNONYMIZER_START_AT='ANONYMIZE_DB'
works fine without settingPYNONYMIZER_INPUT
. In v2 it looks like INPUT has become mandatory - running v2.x against the same set of env vars that worked with v1.x, I get :To Reproduce
as above
Expected behavior
Feels like INPUT should only be mandatory if the
RESTORE_DB
step is going to be in play?Additional context
The text was updated successfully, but these errors were encountered: