As a user I can manage Pulp's database migrations using a systemwide command
In Pulp 2.Y, users use pulp-manage-db to migrate their database when installing for the first time or upgrading to a new version.
It's important that users are able to continue to run migrations in Pulp 3.Y. Since we are leveraging Django's migration management capabilities, Pulp users will need to use the manage.py that is part of the Pulp Django app.
As a result of this story, a new executable should be created. This executable will take the same arguments that manage.py takes and simply forward them to the manage.py in the Pulp app that is installed.
A possible name for the executable is 'pulp-manager'.
#4 Updated by bmbouter about 3 years ago
- Checklist item define the pulp-manager binary as a python entry point added
- Checklist item have all commands be passed along to the manage.py for pulp_app added
- Groomed changed from No to Yes
+1 to this story.
Generically forwarding the commands to manage.py could make the user experience strange/dangerous, but I think as a first-cut at having a utility we should do just this. We can add some filtering later to the forwarded commands.
pulp-manager as the name. We could also use
pulp-config. We can also change this name easily later.
I added some checklist items, and specified that it should be done using a setup.py entrypoint.
I wonder if this would be runnable by any user, or do we need to have it continue to be the apache user?
Please register to edit this issue