When the entry_command feature used in conjunction with hyperdrive config, the backend silently ignores the hyperdrive arguments and defaults to the command specified by the user. It basically disables the use of hyperdrive runs and can mislead users. By switching to entry_script option, this issue can be addressed but users should be notified with warnings or run-time errors if it's caused by azureml-core. Thanks
When the
entry_command
feature used in conjunction with hyperdrive config, the backend silently ignores the hyperdrive arguments and defaults to the command specified by the user. It basically disables the use of hyperdrive runs and can mislead users. By switching toentry_script
option, this issue can be addressed but users should be notified with warnings or run-time errors if it's caused by azureml-core. Thankshttps://github.com/microsoft/hi-ml/pull/909/