Bug 6897

Summary: Customise the Django admin interface
Product: [Build System, Metadata & Runtime] Toaster Reporter: Belen Barros Pena <belen.barros.pena>
Component: toasterAssignee: Unassigned <unassigned>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: Medium CC: alexandru.damian, belen.barros.pena, cristiana.voicu, david.reyna
Version: 1.7   
Target Milestone: Future   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)
Attachments:
Description Flags
Design - Changes to the Django admin interface none

Description Belen Barros Pena 2014-10-27 15:24:13 UTC 
When creating production instances of Toaster, the Toaster administrator will need to use the Django admin interface to create the Toaster releases and configure any layer indexes. This is not straightforward, so we'll need to document how to do it. 

In order to make it a bit easier, we'll try to customise the Django admin interface to help somehow.
Comment 1 Belen Barros Pena 2014-11-05 18:40:36 UTC 
Created attachment 2227 [details]
Design - Changes to the Django admin interface
Comment 2 Belen Barros Pena 2015-02-25 11:20:22 UTC 
The design requires a change in the default variable settings. 

Basically, we'll need to add an option to the Django admin interface, so that administrators can specify if the variable can be empty or not (right now it can't: the admin interface forces you to provide a value). 

If the variable can be empty, it should behave like IMAGE_INSTALL_append (i.e. you can delete the value, but not the variable itself: that can only be done by an administrator). If the variable cannot be empty, then it should behave like the DISTRO does: you can edit the value, but you cannot leave blank or delete the variable.