Actions
Issue #4046
closed
makemigrations seems to ignore custom /etc/pulp/settings.py
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 43
Quarter:
Description
Having a /etc/pulp/settings.py file with:
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.dummy',
'NAME': 'pulp',
'USER': 'pulp',
'HOST': 'foo',
'PORT': '5432',
'CONN_MAX_AGE': 0
},
}
and running 'pulp-manager makemigrations pulp_app'
it seems that the command is still trying to connect to the local postgresql server
Actions
.
Problem: database settings are not being used
Solution: load dynaconf in manage.py, wsgi.py, worker.py, and entry_points.py
This patch introduces a workaround for a dynaconf issue[0].
This patch also changes how Pulp is deployed on Travis. A non-default name is used for the database. That way we will know if the settings in the settings file are being used.
[0] https://github.com/rochacbruno/dynaconf/issues/89
closes: #4046 https://pulp.plan.io/issues/4046