We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
OpenShift 4.6.22, on IBM Cloud
0.7.0
(this example was working in 0.6.0 and stopped working in 0.7.0)
mappings
oc new project sbo oc new-app https://github.com/openshift/ruby-hello-world#beta4 -n sbo oc apply sb-original.yaml oc apply sb-reverse.yaml
All mapped values should be present in the final Secret objects created from the binding.
Secret
Only the mapped values from the one of the services (last in file?) appear in the secrets. The mapped values from the other services are empty.
See two outputs:
oc get secret binding-original-f999dd17 -n sbo -o jsonpath='{.data.env\.json}' | base64 -d | jq . { "Values": [ { "HOST": "ruby-hello-world.sbo.svc.cluster.local", "SOURCE": "<no value>" } ] } root@6d37c76e5d2e:/tools/scripts# oc get secret binding-reverse-18a1300e -n sbo -o jsonpath='{.data.env\.json}' | base64 -d | jq . { "Values": [ { "HOST": "<no value>.<no value>.svc.cluster.local", "SOURCE": "beta4" } ] }
operator-logs.txt
sb-example-archive.zip (contains sb-reverse.yaml and sb-original.yaml)
sb-reverse.yaml
sb-original.yaml
I rolled back the operator to 0.6.0 and saw the correct results again:
oc get secret binding-original-6f93c924eb98fbd528c74b610b632229352734c1 -n sbo -o jsonpath='{.data.env\.json}' | base64 -d | jq . { "Values": [ { "HOST": "ruby-hello-world.sbo.svc.cluster.local", "SOURCE": "beta4" } ] } oc get secret binding-reverse-6f93c924eb98fbd528c74b610b632229352734c1 -n sbo -o jsonpath='{.data.env\.json}' | base64 -d | jq . { "Values": [ { "HOST": "ruby-hello-world.sbo.svc.cluster.local", "SOURCE": "beta4" } ] }
The text was updated successfully, but these errors were encountered:
thanks for the report, I am looking for sb-reverse.yaml and sb-original.yaml but it seems they are not attached?
Sorry, something went wrong.
My mistake, ugh, apologies.
I just attached an archive file containing both.
Successfully merging a pull request may close this issue.
What is the environment (Minikube, Openshift)?
OpenShift 4.6.22, on IBM Cloud
What is the SBO version used?
0.7.0
(this example was working in 0.6.0 and stopped working in 0.7.0)
What are the steps to reproduce this issue?
mappings
section of the binding requestWhat is the expected behaviour?
All mapped values should be present in the final
Secret
objects created from the binding.What is the actual behaviour?
Only the mapped values from the one of the services (last in file?) appear in the secrets.
The mapped values from the other services are empty.
See two outputs:
Service Binding Operator Logs
operator-logs.txt
Additional Information (Screenshots, etc)
sb-example-archive.zip
(contains
sb-reverse.yaml
andsb-original.yaml
)I rolled back the operator to 0.6.0 and saw the correct results again:
The text was updated successfully, but these errors were encountered: