Configuration Options from oslo.config¶
DEFAULT¶
-
config_file¶ Type: list of filenames Default: ~/.project/project.conf,~/project.conf,/etc/project/project.conf,/etc/project.confPath to a config file to use. Multiple config files can be specified, with values in later files taking precedence. Defaults to the value above.
-
config_dir¶ Type: list of directory names Default: ~/.project/project.conf.d/,~/project.conf.d/,/etc/project/project.conf.d/,/etc/project.conf.d/Path to a config directory to pull *.conf files from. This file set is sorted, so as to provide a predictable parse order if individual options are over-ridden. The set is parsed after the file(s) specified via previous –config-file, arguments hence over-ridden options in the directory take precedence.
-
config_source¶ Type: list Default: ''Lists configuration groups that provide more details for accessing configuration settings from locations other than local files.
sample_remote_file_source¶
Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key. Example of using a remote_file source remote_file: A backend driver for remote files served through http[s]. Required options: - uri: URI containing the file location. Non-required options: - ca_path: The path to a CA_BUNDLE file or directory with certificates of trusted CAs. - client_cert: Client side certificate, as a single file path containing either the certificate only or the private key and the certificate. - client_key: Client side private key, in case client_cert is specified but does not includes the private key.
-
driver¶ Type: string Default: remote_fileThe name of the driver that can load this configuration source.
-
uri¶ Type: URI Default: https://example.com/my-configuration.iniRequired option with the URI of the extra configuration file’s location.
-
ca_path¶ Type: string Default: /etc/ca-certificatesThe path to a CA_BUNDLE file or directory with certificates of trusted CAs.
-
client_cert¶ Type: string Default: /etc/ca-certificates/service-client-keystoreClient side certificate, as a single file path containing either the certificate only or the private key and the certificate.
-
client_key¶ Type: string Default: <None>Client side private key, in case client_cert is specified but does not includes the private key.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.