Thanks Evgeniy.

From: Evgeniy L [mailto:[email protected]]
Sent: 24 April 2015 16:39
To: OpenStack Development Mailing List (not for usage questions)
Cc: Joe Marshall
Subject: Re: [openstack-dev] [fuel][plugin] What should go in 
environment_config.yaml when no additional attributes are desired in the Fuel 
Web UI?

Hi Emma,

If you don't need additional elements on UI, just create 
"environment_config.yaml" with
"{}" value for "attributes" key, i.e. "attributes: {}"

Thanks,

On Fri, Apr 24, 2015 at 6:03 PM, Emma Gordon 
(projectcalico.org<http://projectcalico.org>) 
<[email protected]<mailto:[email protected]>> wrote:
The fuel plugin wiki 
https://wiki.openstack.org/wiki/Fuel/Plugins#environment_config.yaml describes 
the required syntax for declaring (in the environment_config.yaml file) 
additional attributes that should appear under the Settings tab of the Fuel Web 
UI. If the only requirement is to have the check box to enable the plugin, but 
no additional attributes, what should go in this file?

I’ve tried not having such a file, leaving it empty, and various variants of 
None/””/[] after ‘attributes:’, but all result in the plugin failing to build – 
the latter due to failing the test_check_env_config_attrs_fail_if_none test in 
https://github.com/stackforge/fuel-plugins/blob/master/fuel_plugin_builder/fuel_plugin_builder/tests/test_validator_v1.py.
 Is it not permitted to have no attributes? Or, if that is a reasonable use 
case, should that test not exist?

Thanks,
Emma

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
[email protected]?subject:unsubscribe<http://[email protected]?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to