We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Mastering Application/Service Configuration

Formal Metadata

Title
Mastering Application/Service Configuration
Subtitle
How to cover your configuration needs with oslo.config
Title of Series
Number of Parts
561
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
This talk covers oslo.config as a replacement option for ConfigParser, ArgumentParser and os.environ integrating all of their main features. Many applications and services rely on configuration data to behave according to a set of specific needs. The standard library gives us ConfigParser, ArgumentParser and os.environ used for easy configuration via plaintext configuration files, command line arguments and environment variables, but they don't come with batteries included to integrate with each other. OpenStack Common Libraries (Oslo) has an enhanced alternative called oslo.config with support to config files, command line arguments, environment, option deprecation, and much more. With the recent addition of source drivers feature, it is also possible to increase the security of config values storing them in a safer place like a secret manager. Using oslo.config over the standard library options is an easy way to achieve flexibility and also become compliant with security matters.