Opened 2 months ago

Closed 2 months ago

#29470 closed New feature (duplicate)

Add output to makemigrations and migrate commands with --noinput

Reported by: Kurt Wheeler Owned by: nobody
Component: Migrations Version: 1.11
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The --noinput option to makemigrations seems to also mean "no output". It would be nice for scripting purposes if there could be some kind of output. When writing a script that helps manage migrations, it would be nice to be able to detect that the migrations needed input from the developer so that the script can fail gracefully and inform the developer that manual intervention is required. Right now the options seem to be to not use the --noinput options and have the prompt interrupt the script, or to use the option and have no idea when migrations failed because they required input.

I'm not very picky as far as how this functionality should be implemented goes. I would think that a little warning like
"No migrations run because input was required but --noinput option was specified."
would be sufficient. This could be output to stdout or stderr, either all the time or perhaps only if an additional option was set.

Change History (1)

comment:1 Changed 2 months ago by Tim Graham

Resolution: duplicate
Status: newclosed

This looks like a similar request as #29026, even if the proposed implementation is a bit different.

Note: See TracTickets for help on using tickets.
Back to Top