A bug surfaced where first time evaluation of a model fails due to the
Model constructor throwing if the model does not exist.

Looking deeper, we see that most calls to get_model expect a possible
None response and check at the call site. Unfortunately we get the same
WebserviceException class for a model not being found as we do a REST
error or similar.

This change is a stopgap mitigation to restore compatibility with the
existing callers, and compromises by allowing the model version
dependent behavior to continue passing on exceptions.

In a future follow up we should settle on a convention and allow version
checks to propagate failure while still giving the possibility for
handling a service exception in the caller.

Recently the step to get the model version had a name associated with the step. We need to also update the references in future step to use the step name as a prefix. This resulted in the MODEL_VERSION variable causing failures in each CD deployment step.

This did not show up in CI because the MODEL_VERSION var is hard coded in the variable group. We should also remove that.

* docs

* fix pipeline status badge and tf naming uniqueness

* add a note about how to change the name of the pipeline

* extra clarification on workspace connection

* fix default params in build batch score

* docs

* fix image

* fix images

* update to azure ml studio pics

* Update ci_dependencies.yml

* Update conda_dependencies.yml

* docs

* more fixes

* Update getting_started.md

* Update custom_model.md

* development_setup.md update

development_setup.md updated to use install_requirements.sh.

See #158:

> Use conda rather than pip packages when possible (as recommended in AML docs).
> Dev environment is hence also constrained to conda (no more pip install -r requirements.txt).

* Content of install_requirements.sh deleted

* build_train_pipeline.py filename fixed

* build_train_pipeline.py filename fixed

TRAIN_SCRIPT_PATH value updated from 'training/train.py' to 'training/train_aml.py'.

This is aligned with /.pipelines/diabetes_regression-variables-template.yml.

Added a clarification, that the AKS compute name comes from the inference cluster, which needs to be created to continue.

* Update conda_dependencies_scoring.yml

* Update conda_dependencies_scorecopy.yml

* Update conda_dependencies_scoring.yml

* Update ci_dependencies.yml

* Update diabetes_regression-cd.yml

* Update diabetes_regression-package-model-template.yml

* Update diabetes_regression-publish-model-artifact-template.yml

* Update conda_dependencies.yml

* Update conda_dependencies_scorecopy.yml

* Update conda_dependencies_scoring.yml

Co-authored-by: Jens Humrich <jens.humrich@siemensgamesa.com>

…m and fix to ARM template to remove region restrictions. (#387)

Co-authored-by: Joao Pedro Martins <joaopedro.martins@microsoft.com>

* Change AKS deployment configuration

Deployment config changed from 1CPU/4GB to 0.5CPU/2GB so it fits a AKS created with default parameters

* Update custom_model.md

Co-authored-by: João Pedro Martins <lokijota@users.noreply.github.com>

* update documentation

* fix evaluate issue

* linting

Co-authored-by: Jens Humrich <jens.humrich@siemensgamesa.com>
Co-authored-by: João Pedro Martins <lokijota@users.noreply.github.com>

* Update manage_environment.py

* Update attach_compute.py

* Update attach_compute.py

* Update manage_environment.py

Co-authored-by: João Pedro Martins <lokijota@users.noreply.github.com>

* Revision of getting started guide up to Batch scoring. Also new diagam and fix to ARM template to remove region restrictions.

* Detail on Batch scoring for Getting Started and additional debug message in the copy to ease of diagnosing issues

* Tweaked text and added a NOQA for message

Co-authored-by: Joao Pedro Martins <joaopedro.martins@microsoft.com>

…ployment (#390)

* Revision of getting started guide up to Batch scoring. Also new diagam and fix to ARM template to remove region restrictions.

* Detail on Batch scoring for Getting Started and additional debug message in the copy to ease of diagnosing issues

* Tweaked text and added a NOQA for message

* Clarified/Fixed getting started instructions for WebApp/AppService deployment

Co-authored-by: Joao Pedro Martins <joaopedro.martins@microsoft.com>