Skip to content

Commit f823be0

Browse files
Addressing review comments and nitpicks
1 parent a28d4f6 commit f823be0

File tree

2 files changed

+26
-26
lines changed

2 files changed

+26
-26
lines changed

modules/sbo-categories-of-exposable-binding-data.adoc

Lines changed: 24 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -41,9 +41,9 @@ metadata:
4141

4242

4343
== Exposing an entire config map or secret that is referenced from a resource
44-
The following examples show how to expose an entire secret as annotations:
44+
The following examples show how to expose an entire secret using annotations:
4545

46-
.Example: Exposing an entire secret as annotations
46+
.Example: Exposing an entire secret through annotations
4747
[source,yaml]
4848
----
4949
apiVersion: postgres-operator.crunchydata.com/v1beta1
@@ -67,9 +67,9 @@ data:
6767
user: "Z3Vlc3Q="
6868
----
6969

70-
The following example shows how to expose an entire config map as OLM descriptors:
70+
The following example shows how to expose an entire config map through OLM descriptors:
7171

72-
.Example: Exposing an entire config map as OLM descriptors
72+
.Example: Exposing an entire config map through OLM descriptors
7373
[source,yaml]
7474
----
7575
- path: data.dbConfiguration
@@ -84,9 +84,9 @@ If you intend to project all the values from a `ConfigMap` service resource, you
8484

8585

8686
== Exposing a specific entry from a config map or secret that is referenced from a resource
87-
The following examples show how to expose a specific entry from a config map as annotations:
87+
The following examples show how to expose a specific entry from a config map through annotations:
8888

89-
.Example: Exposing an entry from a config map as annotations
89+
.Example: Exposing an entry from a config map through annotations
9090
[source,yaml]
9191
----
9292
apiVersion: postgres-operator.crunchydata.com/v1beta1
@@ -111,9 +111,9 @@ data:
111111
user: "hippo"
112112
----
113113

114-
The following example shows how to expose a specific entry from a config map as OLM descriptors:
114+
The following example shows how to expose a specific entry from a config map through OLM descriptors:
115115

116-
.Example: Exposing an entry from a config map as OLM descriptors
116+
.Example: Exposing an entry from a config map through OLM descriptors
117117
[source,yaml]
118118
----
119119
- path: data.dbConfiguration
@@ -129,9 +129,9 @@ This example uses the `path` attribute with an `X-Descriptors` update for `servi
129129

130130

131131
== Exposing a resource definition value
132-
The following example shows how to expose a resource definition value as annotations:
132+
The following example shows how to expose a resource definition value through annotations:
133133

134-
.Example: Exposing a resource definition value as annotations
134+
.Example: Exposing a resource definition value through annotations
135135
[source,yaml]
136136
----
137137
apiVersion: postgres-operator.crunchydata.com/v1beta1
@@ -144,9 +144,9 @@ metadata:
144144
...
145145
----
146146

147-
The following example shows how to expose a resource definition value as OLM descriptors:
147+
The following example shows how to expose a resource definition value through OLM descriptors:
148148

149-
.Example: Exposing a resource definition value as OLM descriptors
149+
.Example: Exposing a resource definition value through OLM descriptors
150150
[source,yaml]
151151
----
152152
- path: data.connectionURL
@@ -160,9 +160,9 @@ If required values are available as attributes of backing service resources, ann
160160

161161

162162
== Exposing entries of a collection with the key and value from each entry
163-
Following is the example for exposing the entries of a collection with the key and value from each entry as annotations:
163+
Following is the example for exposing the entries of a collection with the key and value from each entry through annotations:
164164

165-
.Example: Exposing the entries of a collection as annotations
165+
.Example: Exposing the entries of a collection through annotations
166166
[source,yaml]
167167
----
168168
apiVersion: postgres-operator.crunchydata.com/v1beta1
@@ -193,9 +193,9 @@ The following example shows how the previous entries of a collection in annotati
193193
/bindings/<binding-name>/uri_404 => black-hole.example.com
194194
----
195195

196-
Following is the example for exposing the entries of a collection with the key and value from each entry as OLM descriptors:
196+
Following is the example for exposing the entries of a collection with the key and value from each entry through OLM descriptors:
197197

198-
.Example: Exposing the entries of a collection as OLM descriptors
198+
.Example: Exposing the entries of a collection through OLM descriptors
199199
[source,yaml]
200200
----
201201
- path: bootstrap
@@ -223,9 +223,9 @@ The previous example helps you to project all those values with keys such as `pr
223223

224224

225225
== Exposing items of a collection with one key per item
226-
Following is the example for exposing the items of a collection with one key per item as annotations:
226+
Following is the example for exposing the items of a collection with one key per item through annotations:
227227

228-
.Example: Exposing the items of a collection as annotations
228+
.Example: Exposing the items of a collection through annotations
229229
[source,yaml]
230230
----
231231
apiVersion: postgres-operator.crunchydata.com/v1beta1
@@ -251,9 +251,9 @@ The following example shows how the previous items of a collection in annotation
251251
/bindings/<binding-name>/tags_2 => power
252252
----
253253

254-
Following is the example for exposing the items of a collection with one key per item as OLM descriptors:
254+
Following is the example for exposing the items of a collection with one key per item through OLM descriptors:
255255

256-
.Example: Exposing the items of a collection as OLM descriptors
256+
.Example: Exposing the items of a collection through OLM descriptors
257257
[source,yaml]
258258
----
259259
- path: spec.tags
@@ -274,9 +274,9 @@ spec:
274274

275275

276276
== Exposing values of collection entries with one key per entry value
277-
Following is the example for exposing the values of collection entries with one key per entry value as annotations:
277+
Following is the example for exposing the values of collection entries with one key per entry value through annotations:
278278

279-
.Example: Exposing the values of collection entries as annotations
279+
.Example: Exposing the values of collection entries through annotations
280280
[source,yaml]
281281
----
282282
apiVersion: postgres-operator.crunchydata.com/v1beta1
@@ -305,9 +305,9 @@ The following example shows how the previous values of a collection in annotatio
305305
/bindings/<binding-name>/url_2 => black-hole.example.com
306306
----
307307

308-
Following is the example for exposing the values of collection entries with one key per entry value as OLM descriptors:
308+
Following is the example for exposing the values of collection entries with one key per entry value through OLM descriptors:
309309

310-
.Example: Exposing the values of collection entries as OLM descriptors
310+
.Example: Exposing the values of collection entries through OLM descriptors
311311
[source,yaml]
312312
----
313313
- path: bootstrap

modules/sbo-methods-of-exposing-binding-data.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,8 @@ The service you intend to connect to is compliant with the Service Binding speci
1616
You must expose the binding data from the backing service. Depending on your workload requirements and environment, you can choose any of the following methods to expose the binding data:
1717
+
1818
** Direct secret reference
19-
** Generation of an intermediate secret through custom resource definition (CRD) or CR annotations
20-
** Generation of an intermediate secret through Operator Lifecycle Manager (OLM) descriptors
19+
** Declaring binding data through custom resource definition (CRD) or CR annotations
20+
** Declaring binding data through Operator Lifecycle Manager (OLM) descriptors
2121
** Detection of binding data through owned resources
2222

2323
== Provisioned service

0 commit comments

Comments
 (0)