From f45b411bba5e2cb7dde25117e1c4cdb8a987c525 Mon Sep 17 00:00:00 2001
From: Duncan Doyle <Duncan.Doyle@gmail.com>
Date: Thu, 8 Oct 2020 23:17:10 +0200
Subject: [PATCH] Update README.md

Fixed the ServiceBindingRequest YAML to use the proper "apiVersion" and "kind", and updated the "spec" to use "applicationSelector" and "backingServiceSelector".
---
 examples/nodejs_postgresql/README.md | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/examples/nodejs_postgresql/README.md b/examples/nodejs_postgresql/README.md
index 90ce8b151e..7a1d4aa783 100644
--- a/examples/nodejs_postgresql/README.md
+++ b/examples/nodejs_postgresql/README.md
@@ -182,22 +182,23 @@ Create the following `ServiceBinding`:
 ``` shell
 cat <<EOS |kubectl apply -f -
 ---
-apiVersion: operators.coreos.com/v1alpha1
-kind: ServiceBinding
+apiVersion: apps.openshift.io/v1alpha1
+kind: ServiceBindingRequest
 metadata:
   name: binding-request
   namespace: service-binding-demo
 spec:
-  application:
-    name: nodejs-rest-http-crud
+  applicationSelector:
     group: apps
-    version: v1
     resource: deployments
-  services:
-  - group: postgresql.baiju.dev
-    version: v1alpha1
+    resourceRef: nodejs-rest-http-crud
+    version: v1
+  backingServiceSelector:
+    group: postgresql.baiju.dev
     kind: Database
-    name: db-demo
+    resourceRef: db-demo
+    version: v1alpha1
+  mountPathPrefix: /var/credentialsEOS
 EOS
 ```
 
@@ -209,8 +210,8 @@ make create-service-binding
 
 There are 2 parts in the request:
 
-* `application` - used to search for the application based on the name that we set earlier and the `group`, `version` and `resource` of the application to be a `Deployment`.
-* `services` - used to find the backing service - our operator-backed DB instance called `db-demo`.
+* `applicationSelector` - used to search for the application based on the name that we set earlier and the `group`, `version` and `resource` of the application to be a `Deployment`.
+* `backingServiceSelector` - used to find the backing service - our operator-backed DB instance called `db-demo`.
 
 That causes the application to be re-deployed.