Bug 1463503
Summary: | [PFfBJOsO]Object cannot be return per bind request if contain "." in name | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Wenjing Zheng <wzheng> |
Component: | Service Broker | Assignee: | Jim Minter <jminter> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | DeShuai Ma <dma> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3.6.0 | CC: | aos-bugs, bparees |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-14 18:46:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Wenjing Zheng
2017-06-21 07:06:54 UTC
Good find. Perhaps I should have evaluated the kubernetes jsonpath implementation more closely before using it - this is a second example of the implementation being a bit shaky. It's not documented upstream, but it looks intended that you can work around this issue by escaping the '.' character as follows: "template.openshift.io/expose-how": "{.data['special\\.how']}", I worry that there'll be no appetite for changing this behaviour upstream; I'm inclined to resolve this bz by adding a note to the documentation. @bparees, what do you think? I think documenting the need to escape special characters is a fine resolution. Verified this bug since this is added as a documentation to avoid using special characters. |