This repository has been archived by the owner on Dec 2, 2021. It is now read-only.
Add external key-value store feature to util.env_variables.py #19
Labels
enhancement
New feature or request
As we discussed with the current approach it can be ease to loose track of the variables to be set.
In general I like the approach made here over the variable helper tool:
https://github.com/liupeirong/MLOpsManufacturing/blob/main/ml_service/util/env_variables.py
I see a big potential if we enable this helper tool to be able to switch between ENV variables (or a YAML file representation) and a Key-Value Store like App Configuration Service.
This will also help to reduce redefinition of "env" variables within a Azure Pipeline, either the values are directly retrieved while the python modules are executed or we could even leverage the Azure Pipeline task for App Configuration Service.
In addition we could also keep track of configuration changes, a feature provided by App Configuration Service.
Still I see a need to classify the variables/parameters regarding their purpose to decide where to store them and which degree of approval is needed to change them. E.g. is the variable/parameter relevant to describe the infrastructure, are they relevant to describe the source data, training parameters, model attributes, secrets etc.
The text was updated successfully, but these errors were encountered: