e8e84c2db4
This patch enables all of the features for the Flavors panel to use Angular but disables it, so that it is easy to switch on/off. Note that we add integration test switches since it can't read the Django conf. Note that I changed the common tests to allow for testing of api calls that don't produce error toasts, because we needed better branch coverage, and the deleteFlavor api wasn't fully branch-tested. Change-Id: I92b1b57bd486e5eb87179cb8d44b7551e9de2e0f Partially-Implements: blueprint ng-flavors
14 lines
540 B
YAML
14 lines
540 B
YAML
---
|
|
prelude: >
|
|
The Flavor panel now may be configured to use
|
|
either the legacy or Angular code.
|
|
features:
|
|
- ANGULAR_FEATURES now allows for a key 'flavors_panel' to be
|
|
specified as True or False indicating whether the Angular
|
|
version of the panel is enabled.
|
|
- Integration tests for Flavor features may also be toggled
|
|
in openstack_dashboard/test/integration_tests/horizon.conf
|
|
using the 'panel_type' feature in the 'flavors' setting,
|
|
either set to 'legacy' or 'angular' to match the enabled
|
|
panel type.
|