Ok thanks. I'm also using --skip-task-init because i'm manually initializing a task and connecting configurations in my_script. I guess then the get_parameters won't give what i'm looking for?
I have a specific situation, maybe you can help me with this
my_script looks something like this
thirdparty_argparser1() [...my_code...] thirdparty_argparser2()I cannot interfere with implementations of these thirdparty argparsers. The first argparser expects arg1=val1 --arg2=val2 , and the second expects arg1=val1 . The problem is that thirdparty_argparser2 also has an optional arg2, but of a different data type. I actually do not need the --arg2 in the thirdparty_argparser2 , but it still fails because it is automagically forwarded from the --args... Do you know how i could intercept this? (without changing the thirdparty_argparser2 implementation)
Thanks