You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/workflows/pr.yml
+2-4Lines changed: 2 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -56,9 +56,7 @@ jobs:
56
56
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Needed to get PR information
57
57
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }} # Generate a token on Sonarcloud.io, add it to the secrets of this repo with the name SONAR_TOKEN (Settings > Secrets > Actions > add new repository secret)
58
58
with:
59
-
# Additional arguments for the sonarcloud scanner
60
59
args:
61
-
# Unique keys of your project and organization. You can find them in SonarCloud > Information (bottom-left menu)
Package used for retrieving application settings from various sources.
@@ -154,7 +149,10 @@ For Azure KeyVault the first part of the token needs to be the name of the vault
154
149
For HashicorpVault the first part of the token needs to be the name of the mountpath. In Dev Vaults this is `"secret"`,
155
150
e.g.:
156
151
157
-
`VAULT://secret/demo/configmanager|test`
152
+
`VAULT://secret___demo/configmanager|test`
153
+
154
+
The hardcoded separator cannot be modified and you must separate your `mountPath` with `___` (3x `_`) followed by the key to the secret.
155
+
158
156
159
157
The Hashicorp Vault functions in the same exact way as the other implementations. It will retrieve the JSON object and can be looked up within it by using a key separator.
0 commit comments