pdb_load_data no longer creates necessary org usergroups #1480
Comments
|
Verified bug. |
vegu
pushed a commit
that referenced
this issue
Feb 20, 2024
Merged
grizz
pushed a commit
that referenced
this issue
Feb 20, 2024
* Add field ixf_ixp_import_enabled to object ixlan #1229 pdb_load_data no longer creates necessary org usergroups #1480 API list net documentation says "org" is a string, but it actually contains a dictionary #1438 Allow users to edit their objects Geocode #1464 * escape lat lng input * only notify for `ok` facilities linting --------- Co-authored-by: 20C <code@20c.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
We use
pdb_load_datato sync developer instances and the tutorial instance with data from the api.We upgraded to use the new peeringdb client to handle the sync logic, however since that now does batch inserts this no longer triggers the necessary signals for organization user groups to be created during import.
This effects developers wanting to import data into their instance as well as the tutorial server which also uses this command to get up to date data once in a while.
To Reproduce
Steps to reproduce the behavior:
manage.py pdb_wipemanage.py pdb_load_data/cp/auth/group/and note that all the organization groups are missingExpected behavior
Wiping and importing data via pdb_load_data should create all the necessary organization user groups for the orgs it imports.
Who is affected by the problem?
Developers, users of the tutorial server
Are there security concerns?
No
Are there privacy concerns?
No
What are the proposed actions?
Make sure pdb_load_data calls all the necessary signals. Double check signals.py if anything else is missing.
The text was updated successfully, but these errors were encountered: