Reviewed: https://review.openstack.org/550468
Committed:
https://git.openstack.org/cgit/openstack/api-wg/commit/?id=b585c8485d86c2ec9bc19d9f99ab442f9b375374
Submitter: Zuul
Branch:master
commit b585c8485d86c2ec9bc19d9f99ab442f9b375374
Author: Chris Dent
Date: Wed Mar
I'm tempted to consider such HTTP headers modification as a feature as
per the Nova policy about bugs vs. features, hence the Wishlist
importance.
I also wonder if it would be better to rather create a blueprint in
https://blueprints.launchpad.net/nova/ and add a new spec if it needs an
API
I've added api-sig to this because the fact that this issue has shown up
in the wild should be good motivation for us to make a guideline about
how to address it. The code for adding the requisite headers to
placement may be a useful starting point:
https://review.openstack.org/#/c/521640/
**
3 matches
Mail list logo