1050755d05
We should unify the angular features (new panels, workflows, etc.) in a single setting. This also makes it a little cleaner to read, simply using the 'truthiness' of a key rather than string comparisons. I haven't moved the 'swift_panel' setting, as that panel will be removed in the O cycle anway, so it seems pointless to move a setting causing potential issues for a single cycle. Change-Id: Ia5702ff523355ae895e14cc3d49c895128478944
14 lines
558 B
YAML
14 lines
558 B
YAML
---
|
|
prelude: >
|
|
The Images panel now may be configured to use
|
|
either the legacy or Angular code.
|
|
features:
|
|
- the ``ANGULAR_FEATURES`` setting now allows for a key
|
|
``images_panel``. If set to ``True``, then the Angular
|
|
Images panel will be used, while the Python version will
|
|
be used if set to ``False``.
|
|
- Integration tests for Image features may also be toggled
|
|
in openstack_dashboard/test/integration_tests/horizon.conf
|
|
using the 'panel_type' feature, either set to 'legacy' or
|
|
'angular' to match the enabled panel type.
|