expose creation APIRequestInfoResolver

[deads2k]

No one outside of the apiserver package can create or inspect the APIRequestInfoResolver. OpenShift would like to do both: "create my own APIRequestInfoResolver", "what APIPrefixes are being used", "what resources are recognized", etc.

@smarterclayton pretty small, but needed for unification.

[googlebot]

Thanks for your pull request.

It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA) at https://cla.developers.google.com/.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check the information on your CLA or see this help article on setting the email on your git commits.

Once you've done that, please reply here to let us know. If you signed the CLA as a corporation, please let us know the company's name.

[deads2k]

lawyer bot is fast!

[smarterclayton]

I'm increasingly disatisfied with apirequestinforesolver. Let me look at this but I may ask you to start mitigating that concern.

On Feb 16, 2015, at 1:57 PM, David Eads [email protected] wrote:

No one outside of the apiserver package can create or inspect the APIRequestInfoResolver. OpenShift would like to do both: "create my own APIRequestInfoResolver", "what APIPrefixes are being used", "what resources are recognized", etc.

@smarterclayton pretty small, but needed for unification.

You can view, comment on, or merge this pull request online at:

#4461

Commit Summary

expose creation APIRequestInfoResolver
File Changes

M pkg/apiserver/handlers.go (8)
Patch Links:

https://github.com/GoogleCloudPlatform/kubernetes/pull/4461.patch
https://github.com/GoogleCloudPlatform/kubernetes/pull/4461.diff
—
Reply to this email directly or view it on GitHub.

[smarterclayton]

I guess this is fine as is. LGTM