Skip to content

Commit 4d6a401

Browse files
committed
Update README.md
Update to readme to address this change in how pipeline token secrets should be created. This question popped up on rocketchat to
1 parent 02742dc commit 4d6a401

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,9 @@ Here is the arrangement of secrets, variables and environments for this reposito
111111

112112
**`OC_TOKEN`** 🎫
113113

114-
OpenShift's service account token, different for every namespace. This guide assumes your OpenShift platform team has provisioned a pipeline account.
114+
OpenShift service account token, different for every namespace. This guide assumes your team has provisioned a pipeline account in OpenShift. If not, you can create one by following the instructions [here](https://github.com/bcgov/gh-discussions-lab/discussions/3750).
115+
116+
*Note:* In earlier versions of OpenShift, a pipeline token secret was created automatically in each namespace.
115117

116118
* Consume: `{{ secrets.OC_TOKEN }}`
117119

0 commit comments

Comments
 (0)