Fix ordering of swift3 in middleware pipeline

Beginning with commit 6ffcc29 of swift3, the swift3 and s3token middlewares
must come between authtoken and keystoneauth in the swift proxy pipeline.

When 6ffcc29 was committed, reordering was optional at the expense of an
unneceessary call to keystone.  However, the change becomes mandatory when using
keystone v3 tokens.  Without this change, authtoken will strip the necessary
headers that s3token just added to the environment.

Change-Id: Ic7d07d869aa617ee00190a9aedf411017539b97b
(cherry picked from commit 8b2fc7afc7)
This commit is contained in:
Charles Farquhar 2017-07-27 15:51:40 -05:00 committed by Jesse Pretorius (odyssey4me)
parent f558191108
commit 0946e99dbd
1 changed files with 2 additions and 2 deletions

View File

@ -85,13 +85,13 @@ swift_middleware_list:
- proxy-logging
- "{% if swift_ceilometer_enabled | bool %}ceilometer{% endif %}"
- cache
- "{% if swift_swift3_enabled | bool%}swift3{% endif %}"
- "{% if swift_swift3_enabled | bool%}s3token{% endif %}"
- container_sync
- bulk
- tempurl
- ratelimit
- authtoken
- "{% if swift_swift3_enabled | bool%}swift3{% endif %}"
- "{% if swift_swift3_enabled | bool%}s3token{% endif %}"
- keystoneauth
- staticweb
- copy