hi all,
there have been a few reviews recently where the issue of service type
versus project name have come up for use in the headers. as usual this
conversation can get quite murky as there are several good examples
where service type alone is not sufficient (for example if a service
exposes several api controllers), and as has been pointed out project
name can also be problematic (for example projects can change name).
i'm curious if we could come to a consensus regarding the use of service
type *or* project name for headers. i propose leaving the ultimate
decision up to the projects involved to choose the most appropriate
identifier for their custom headers.
i am not convinced that we would ever need to have a standard on how
these names are chosen for the header values, or if we would even need
to have header names that could be deduced. for me, it would be much
better for the projects use an identifier that makes sense to them,
*and* for each project to have good api documentation.
so, instead of using examples where we have header names like
"OpenStack-Some-[SERVICE_TYPE]-Header", maybe we should suggest
"OpenStack-Some-[SERVICE_TYPE or PROJECT_NAME]-Header" as our guideline.
for reference, here are the current reviews that are circling around
this issue:
https://review.openstack.org/#/c/243429
https://review.openstack.org/#/c/273158
https://review.openstack.org/#/c/243414
and one that has already been merged:
https://review.openstack.org/#/c/196918
thoughts?
regards,
mike
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
