98a13bc212
This adds the CORS support middleware to CloudKitty, allowing a deployer to optionally configure rules under which a javascript client may break the single-origin policy and access the API directly. For CloudKitty, we used the same gabbi fixtures and harnesses created for ceilometer. A custom gabbi-paste.ini was created so that the API tests run against the full wsgi application, and appropriate fixtures and tests were created to correctly simulate the configuration state. Hooks to ensure that cloudkitty's required HTTP headers are represented both in the runtime defaults, and in the automatically generated config file, have also been added. OpenStack CrossProject Spec: http://specs.openstack.org/openstack/openstack-specs/specs/cors-support.html Oslo_Middleware Docs: http://docs.openstack.org/developer/oslo.middleware/cors.html OpenStack Cloud Admin Guide: http://docs.openstack.org/admin-guide-cloud/cross_project_cors.html DocImpact: Add link to CORS configuration in admin cloud guide. Change-Id: I3ef96ca6c78c5e369fb09425871d0a57bf15ad8a |
||
|---|---|---|
| .. | ||
| cloudkitty | ||
| oslo-config-generator | ||