Due to the way django validates fields having a required=True fieild
almoust never makes sense. This would mean that user would not be able
to choose false for the boolean value, that the Field represents,
because django would raise an error, stating, that the field is
required.
This is especially true for fields, generated for HOT template-packages.
This patch sets required to False for dynamic_ui.
Reviewed: https:/ /review. openstack. org/185751 /git.openstack. org/cgit/ openstack/ murano- dashboard/ commit/ ?id=cd380da63d9 5c8a546792c5de2 5cdc19a4070466
Committed: https:/
Submitter: Jenkins
Branch: master
commit cd380da63d95c8a 546792c5de25cdc 19a4070466
Author: Kirill Zaitsev <email address hidden>
Date: Wed May 27 00:38:26 2015 +0300
Mark BooleanFields as non-required in dynamic_ui
Due to the way django validates fields having a required=True fieild
almoust never makes sense. This would mean that user would not be able
to choose false for the boolean value, that the Field represents,
because django would raise an error, stating, that the field is
required.
This is especially true for fields, generated for HOT template-packages.
This patch sets required to False for dynamic_ui.
Change-Id: Ibc36017e37bb7d f9f7bde2c532652 37b21276fd6
Related-Bug: #1450536