Issue #4046: makemigrations seems to ignore custom /etc/pulp/settings.py - Pulp

Actions

Send by e-mail Copy link

Issue #4046

closed

makemigrations seems to ignore custom /etc/pulp/settings.py

Added by jsherril@redhat.com about 6 years ago. Updated about 5 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

dkliban@redhat.com

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Groomed:

Sprint Candidate:

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

Copy link

Updated by dkliban@redhat.com about 6 years ago

Status changed from NEW to POST
Assignee set to dkliban@redhat.com
Sprint set to Sprint 43
Tags Pulp 3 added

https://github.com/pulp/pulp/pull/3678/files

Actions

Copy link

Updated by dkliban@redhat.com about 6 years ago

Status changed from POST to ASSIGNED

The patch I posted earlier only works for the web server. The RQ worker is still not seeing custom database settings.

Added by dkliban@redhat.com about 6 years ago

Revision 617c916e | View on GitHub

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

Added by dkliban@redhat.com about 6 years ago

Revision 617c916e | View on GitHub

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

Actions

Copy link