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
Currently, when setting the -t flag, the script will always use test.yml as input but it should be possible to hav all these options:
1.) Test mode with environment.yml
2.) Test mode with custom .yml file provided with -y
3.) No test mode with environment.yml
4.) No test mode custom .yml file provided with -y
I think this could be solved with nested getopts.
When -t is provided without -y, always fall back to test.yml
When -y is provided without -t, always fall back to no running testing mode
The text was updated successfully, but these errors were encountered:
Currently, when setting the
-t
flag, the script will always usetest.yml
as input but it should be possible to hav all these options:1.) Test mode with environment.yml
2.) Test mode with custom .yml file provided with -y
3.) No test mode with environment.yml
4.) No test mode custom .yml file provided with -y
I think this could be solved with nested getopts.
The text was updated successfully, but these errors were encountered: