Import private.py in devstack_docker.py files instead of devstack.py (#23512)

Background: I use private.py a lot in my devstack for my private configurations. But issues are raised when I need to change/override a setting that is defined in devstack_docker.py file. Since that file's contents are loaded after private.py, my private.py is useless against the settings in devstack_docker.py.

Description: Now that the devstack is dockerized, I think it makes more sense to import the private.py in the devstack_docker.py files i.e. at the end of configuration files hierarchy.
This commit is contained in:
Danial Malik
2020-03-30 18:38:25 +05:00
committed by GitHub
parent 0aba1af792
commit 8d951ae8ae
4 changed files with 10 additions and 10 deletions

View File

@@ -183,11 +183,6 @@ plugin_settings.add_plugins(__name__, plugin_constants.ProjectType.CMS, plugin_c
OPENAPI_CACHE_TIMEOUT = 0
###############################################################################
# See if the developer has any local overrides.
if os.path.isfile(join(dirname(abspath(__file__)), 'private.py')):
from .private import * # pylint: disable=import-error,wildcard-import
#####################################################################
# Lastly, run any migrations, if needed.
MODULESTORE = convert_module_store_setting_if_needed(MODULESTORE)