#24820: Add functionality to handle keyboard prompts during migrations for
automated deployments
-------------------------------------+-------------------------------------
     Reporter:  Protosac             |                    Owner:  nobody
         Type:  New feature          |                   Status:  closed
    Component:  Migrations           |                  Version:  1.7
     Severity:  Normal               |               Resolution:  wontfix
     Keywords:  migration,           |             Triage Stage:
  automatic deployment               |  Unreviewed
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by timgraham):

 The title seems to suggest building a framework that's capable of
 responding to input prompts when they appear. This seems quite different
 from the solution of allowing one particular function to be invoked in a
 particular way (bypassing the input prompt). I would expect the title of
 the new ticket to be something like "Add a function to delete stale
 content types that doesn't require interaction".

 What I meant about ignoring `interactive` is that there isn't a behavior
 difference between:
 {{{
 update_contenttypes(interactive=True, force_remove=True)
 update_contenttypes(interactive=False, force_remove=True)
 }}}
 `interactive` has no effect if `force_remove=True`. Since
 `update_contenttypes()` isn't a documented, public API, one solution might
 be to create a new simpler function in somewhere like
 `contenttypes/utils.py` with less confusing arguments (it might invoke
 `update_contenttypes()` with some 'private' argument like `force_remove`
 as you suggested).

--
Ticket URL: <https://code.djangoproject.com/ticket/24820#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.909a5ce0396a3b015c656dd81fde3a8a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to