Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capture X-Api-Info-Location header in all broker requests #67

Merged
merged 1 commit into from
Jun 26, 2019

Conversation

vorbidan
Copy link
Contributor

@vorbidan vorbidan commented Jun 14, 2019

Add infoLocation to context. This will allow to ping back the platform and obtain additional details if required.

@cf-gitbot
Copy link
Member

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/166713902

The labels on this github issue will be updated when the story is started.

@mattmcneeney
Copy link

Note the relevant change to the OSBAPI spec being discussed here: openservicebrokerapi/servicebroker#676

@vorbidan
Copy link
Contributor Author

Yeah, that is also me at openservicebrokerapi/servicebroker#676 talking about the same issue. The difference is the implementation vs. the spec. BTW, Spring Cloud Service broker implements this header since earlier versions...

@gabrielecipriano gabrielecipriano merged commit 45c6cc1 into pivotal-cf:master Jun 26, 2019
@kirederik
Copy link
Contributor

We'll keep an eye on the discussion and update the implementation if needed.

In the meanwhile, we see no problem in merging this in.

Thanks @vorbidan !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants