Project

Profile

Help

Send by e-mail

Issue #4077

pulpcore can't be installed in a Django site that also ships a a custom User object

Added by bmbouter about 1 year ago. Updated 6 months ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
3.0
Start date:
Due date:
Severity:
2. Medium
Version:
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

Problem

The pulpcore app isn't "reusable" because of this. See https://docs.djangoproject.com/en/2.1/topics/auth/customizing/#reusable-apps-and-auth-user-model

Solution

I'm not sure of all the implications but we could:

(a) stop shipping a custom user model entirely.
(b) move the user bits to their own python package
(c) find an existing Django app that users can install/configure that is effectively solution (b)

Associated revisions

Revision aa519c8e View on GitHub
Added by bmbouter about 1 year ago

Removes custom User model

https://pulp.plan.io/issues/4077
closes #4077

Revision aa519c8e View on GitHub
Added by bmbouter about 1 year ago

Removes custom User model

https://pulp.plan.io/issues/4077
closes #4077

Revision aa519c8e View on GitHub
Added by bmbouter about 1 year ago

Removes custom User model

https://pulp.plan.io/issues/4077
closes #4077

Revision b2471634 View on GitHub
Added by Alexander Saprykin 12 months ago

Fix user serializer for custom user model

In case of custom user model used, PasswordSerializer fails
because it relies on builtin into Django user model.
This patch add dynamic user model resolving.

closes #4077

Revision b2471634 View on GitHub
Added by Alexander Saprykin 12 months ago

Fix user serializer for custom user model

In case of custom user model used, PasswordSerializer fails
because it relies on builtin into Django user model.
This patch add dynamic user model resolving.

closes #4077

Revision b2471634 View on GitHub
Added by Alexander Saprykin 12 months ago

Fix user serializer for custom user model

In case of custom user model used, PasswordSerializer fails
because it relies on builtin into Django user model.
This patch add dynamic user model resolving.

closes #4077

History

#1 Updated by bmbouter about 1 year ago

This is blocking the integration with galaxy.ansible.com

#2 Updated by bmbouter about 1 year ago

I posted a possible fix in this PR here: https://github.com/pulp/pulp/pull/3711/files

#3 Updated by bmbouter about 1 year ago

  • Status changed from NEW to POST

#4 Updated by bmbouter about 1 year ago

  • Status changed from POST to MODIFIED

#5 Updated by bmbouter 12 months ago

  • Status changed from MODIFIED to POST

Moving to post to attach another issue

#6 Updated by CodeHeeler 12 months ago

  • Triaged changed from No to Yes

#7 Updated by Anonymous 12 months ago

  • Status changed from POST to MODIFIED

#8 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#9 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Send by e-mail

Also available in: Atom PDF