Hello, we are in the process of upgrading our serv...
# ask-for-help
t
Hello, we are in the process of upgrading our services from 1.1 to 1.3. In the past, we have utilized configuration overrides with environmental variables. Is this possible in 1.3 or is the only way to set configuration variables like timeout and number of workers in the service definition?
Our use case is that we are deploying our bentos in kubernetes and sometimes we deploy the service with GPU's and sometimes we don't. We liked to set the configuration parameters via env variables for each of those situations differently
j
I believe BENTOML_CONFIG_OPTIONS would still work and take precedence over the code decorator definition, and of course since you can define the variable in code, you can always inject your own environment variable
s
Thanks for your reply @Jian Shen Yap. We tried
BENTOML_CONFIG_OPTIONS
but didn't work. Do you have an example of the definition for BENTOML_CONFIG_OPTIONS for bentoml 1.3? Is
BENTOML_CONFIG_OPTIONS='services.MyService1.workers=1 services.MyService2.workers=3' bentoml serve ...
the correct way?
It looks like
BENTOML_CONFIG_OPTIONS='services.MyService1.workers=1 services.MyService2.workers=3'
works for us. It would be nice if it is documented in bentoml doc.
j
Thanks! We will update the docs accordingly! otherwise, contribution is welcomed too