The new CLI writes all the parameters to config.yaml to keep track of all the parameters run. However, if the users have specified a flag, and the flag will be set to True in the config.yaml and users may not be aware of that when using the config.yaml later.
What was done?
Instead of writing all the parameters used in the step to config.yaml, only non-flag parameters get written to the config.yaml. Flags specified in config.yaml won't get updated.
How Has This Been Tested?
CI and locally
Breaking Changes
NA
Checklist:
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation
Issue being fixed or feature implemented
The new CLI writes all the parameters to
config.yamlto keep track of all the parameters run. However, if the users have specified a flag, and the flag will be set to True in theconfig.yamland users may not be aware of that when using theconfig.yamllater.What was done?
Instead of writing all the parameters used in the step to
config.yaml, only non-flag parameters get written to the config.yaml. Flags specified in config.yaml won't get updated.How Has This Been Tested?
CI and locally
Breaking Changes
NA
Checklist: