Not Considering

CIL has been deprecated therefore no improvements for it will be provided anymore. Please consider alternatives in the later versions of the product. 

Allow usage of Environment Variables in web.config (or app.config) for CIL settings

The (.NET) CIL reads the connection settings for the discovery service from an app.config or web.config. Typically this will consist of:

  • discovery-service-uri
  • oauth-enabled
  • oauth-client-id
  • oauth-client-secret

It would be great if we could use environment variables for these values (as shown here: http://stackoverflow.com/a/29416404/866454) instead of having to enter this information in the config files.

Nuno Linhares
Parents

  • Working with environment variables instead of configuration seems to be the container-friendly way forward. But what are the expectations when you have both (say legacy) config files and want to use environment variables in the creation of a container, instance, or whatever? Does one take precedence over the other? Or should configs always have placeholders for the values you want to come from the environment?

Comment

  • Working with environment variables instead of configuration seems to be the container-friendly way forward. But what are the expectations when you have both (say legacy) config files and want to use environment variables in the creation of a container, instance, or whatever? Does one take precedence over the other? Or should configs always have placeholders for the values you want to come from the environment?

Children
No Data