Issue #1649: The [lazy] `enabled` setting in server.conf is not a valuable setting and should be removed. - Pulp

Send by e-mail

Issue #1649

The [lazy] `enabled` setting in server.conf is not a valuable setting and should be removed.

Added by jcline@redhat.com about 5 years ago. Updated almost 2 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

jcline@redhat.com

Category:

Sprint/Milestone:

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

2.8.0

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Pulp 2

Sprint:

Quarter:

Description

There is a configuration option for lazy, 'enabled', that must be set to true or the content WSGI application doesn't redirect. If the content WSGI application always redirected (and this setting didn't exist), the only difference is that the client would get a 302 redirect and then a 404 or 503 if they haven't set up the lazy services. This isn't harmful, and it makes it easier to debug.

Therefore we should remove it before releasing 2.8 and being stuck with a pointless setting.

Associated revisions

Revision 0f100dbb View on GitHub
Added by Jeremy Cline about 5 years ago

Remove the enabled setting for lazy.

This setting didn't do anything beyond stopping the content WSGI application from redirecting the client. If the lazy services haven't been setup, the client will receive a HTTP 503 or HTTP 404.

closes #1649

Revision 0f100dbb View on GitHub
Added by Jeremy Cline about 5 years ago

Remove the enabled setting for lazy.

This setting didn't do anything beyond stopping the content WSGI application from redirecting the client. If the lazy services haven't been setup, the client will receive a HTTP 503 or HTTP 404.

closes #1649