- Registered on: 10/14/2019
- Last connection: 04/12/2021
- Ansible Plugin (Developer, 10/16/2019)
We don't have an immediate need to get this fixed in 3.11 for galaxy_ng. Issue #8048: Object permissions endpoint breaks for objects with unknown viewsetsWhen I visit `http://localhost:5001/pulp/api/v3/groups/1/object_permissions/` I get the error bellow.
It appears as though the `object_permissions/` viewset is trying to look up a `ViewSet` name on the galaxy_ng `Namepsace` model, whi...
Applied in changeset commit:pulpcore|702d904863e8ffd9732e5a08acf271de396fc72f. Issue #8375 (MODIFIED): As a plugin writer I have the ability to query a repository for a specific content typeAllow for plugin writers to query a specific content type in a repository and get back the correct django model for that content type.
That's sort of worrying. Those versions were uploaded recently (within the last 2 months). This makes me think we're not properly validating collections at import time. Issue #8292: FILES.json not found when syncing all of galaxy.ansible.com~~~
Feb 22 18:24:22 ip-172-32-0-61 rq: pulp [c1c01c8eb5b4411dafd848e54fe8148e]: pulp_ansible.app.tasks.utils:INFO: Reading meta/runtime.yml from artifact/c2/939ffe56fe75ffd1ae96e6f0159421aa120c286a9464ac851bb00c25568e42
Feb 22 ...
(cherry picked from commit 0aaeef4e535170b38d81a644ad56a2a86dd7e7fd) Revision cb3302de (pulp_container): Use get_user_model instead of auth.models.user
(cherry picked from commit 0aaeef4e535170b38d81a644ad56a2a86dd7e7fd) Revision cb3302de: Use get_user_model instead of auth.models.user
Applied in changeset commit:0aaeef4e535170b38d81a644ad56a2a86dd7e7fd. Issue #8260 (MODIFIED): Use get_user_model instead of auth.models.usermporting and using django.contrib.auth.models.User breaks any apps that use custom user models defined in AUTH_USER_MODEL. To prevent this from happening, the User model should be loaded using django's get_user_model() function.
Also available in: Atom