Skip to content

Commit eca3112

Browse files
revert wording changes
Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
1 parent 3d87a6f commit eca3112

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

standards/certification/pipeline.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ We are going to create a pull request that is very similar to real-life example
108108

109109
Again, insert your subject so that the list (after `gx-scs`) remains sorted.
110110

111-
4. Finally, add application credentials to [.zuul.d/secure.yaml](https://github.com/SovereignCloudStack/standards/blob/main/.zuul.d/secure.yaml).
111+
4. Finally, add secrets to [.zuul.d/secure.yaml](https://github.com/SovereignCloudStack/standards/blob/main/.zuul.d/secure.yaml).
112112
This is necessary so the tests can access your cloud.
113113

114114
:::info
@@ -179,7 +179,7 @@ We are going to create a pull request that is very similar to real-life example
179179
You may have to adapt these instructions to your infrastructure. For instance, the application credentials
180180
we create here are stored locally. If you want to include the check suite into your own
181181
continuous-integration pipeline, you may want to use some dedicated credential store and mechanism for
182-
injecting application credentials.
182+
injecting secrets.
183183

184184
You may want to take inspiration from our own Zuul setup by looking at
185185
[.zuul.d](https://github.com/SovereignCloudStack/standards/tree/main/.zuul.d) and

0 commit comments

Comments
 (0)