Skip to content

Commit 4d20963

Browse files
authoredJan 31, 2024
Merge pull request #609 from stakater/vale-package
Switch from submodule to Vale package for spell checking
2 parents 223ed53 + e9b09e7 commit 4d20963

File tree

8 files changed

+26
-13
lines changed

8 files changed

+26
-13
lines changed
 

‎.github/workflows/pull_request.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ env:
1414

1515
jobs:
1616
qa:
17-
uses: stakater/.github/.github/workflows/pull_request_doc_qa.yaml@v0.0.62
17+
uses: stakater/.github/.github/workflows/pull_request_doc_qa.yaml@v0.0.64
1818
with:
1919
MD_CONFIG: .github/md_config.json
2020
DOC_SRC: README.md docs

‎.gitignore

+2-1
Original file line numberDiff line numberDiff line change
@@ -11,4 +11,5 @@ vendor
1111
dist
1212
Reloader
1313
!**/chart/reloader
14-
*.tgz
14+
*.tgz
15+
styles/

‎.gitmodules

-3
This file was deleted.

‎.vale.ini

+3-2
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
1-
StylesPath = "vocabulary/styles"
1+
StylesPath = styles
22
MinAlertLevel = warning
33

4-
Vocab = "Stakater"
4+
Packages = https://github.com/stakater/vale-package/releases/download/v0.0.6/Stakater.zip
5+
Vocab = Stakater
56

67
# Only check MarkDown files
78
[*.md]

‎README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -308,9 +308,9 @@ Reloader can be configured to only watch configmaps/secrets labeled with one or
308308

309309
**Note:** Both `namespaceSelector` & `resourceLabelSelector` can be used together. If they are then both conditions must be met for the configmap or secret to be eligible to trigger reload events. (e.g. If a configMap matches `resourceLabelSelector` but `namespaceSelector` does not match the namespace the configmap is in, it will be ignored).
310310

311-
You can also set the log format of Reloader to json by setting `logFormat` to `json` in values.yaml and apply the chart.
311+
You can also set the log format of Reloader to JSON by setting `logFormat` to `json` in `values.yaml` and apply the chart.
312312

313-
You can enable to scrape Reloader's Prometheus metrics by setting `serviceMonitor.enabled` or `podMonitor.enabled` to `true` in values.yaml file. Service monitor will be removed in future releases of Reloader in favour of Pod monitor.
313+
You can enable to scrape Reloader's Prometheus metrics by setting `serviceMonitor.enabled` or `podMonitor.enabled` to `true` in `values.yaml` file. Service monitor will be removed in future releases of Reloader in favour of Pod monitor.
314314

315315
**Note:** Reloading of OpenShift (DeploymentConfig) and/or Argo `Rollouts` has to be enabled explicitly because it might not be always possible to use it on a cluster with restricted permissions. This can be done by changing the following parameters:
316316

@@ -321,7 +321,7 @@ You can enable to scrape Reloader's Prometheus metrics by setting `serviceMonito
321321
| reloadOnCreate | Enable reload on create events. Valid value are either `true` or `false` | boolean |
322322
| syncAfterRestart | Enable sync after Reloader restarts for **Add** events, works only when reloadOnCreate is `true`. Valid value are either `true` or `false` | boolean |
323323

324-
**isOpenShift** Recent versions of OpenShift (tested on 4.13.3) require the specified user to be in an uid range which is dynamically assigned by the namespace. The solution is to unset the runAsUser variable via ``deployment.securityContext.runAsUser=null`` and let OpenShift assign it at install.
324+
**isOpenShift** Recent versions of OpenShift (tested on 4.13.3) require the specified user to be in an `uid` range which is dynamically assigned by the namespace. The solution is to unset the runAsUser variable via ``deployment.securityContext.runAsUser=null`` and let OpenShift assign it at install.
325325

326326
**ReloadOnCreate** reloadOnCreate controls how Reloader handles secrets being added to the cache for the first time. If reloadOnCreate is set to true:
327327

‎docs/Alerting.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Reloader can alert when it triggers a rolling upgrade on Deployments or Stateful
44

55
## Enabling the feature
66

7-
In-order to enable this feature, you need to update the `reloader.env.secret` section of values.yaml providing the information needed for alert.
7+
In-order to enable this feature, you need to update the `reloader.env.secret` section of `values.yaml` providing the information needed for alert:
88

99
```yaml
1010
ALERT_ON_RELOAD: [ true/false ] Default: false

‎renovate.json

+16-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,21 @@
11
{
22
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
33
"extends": [
4-
"config:base"
4+
"config:recommended"
5+
],
6+
"labels": [
7+
"dependencies"
8+
],
9+
"customManagers": [
10+
{
11+
"customType": "regex",
12+
"fileMatch": [
13+
".vale.ini"
14+
],
15+
"matchStrings": [
16+
"https:\/\/github\\.com\/(?<depName>.*)\/releases\/download\/(?<currentValue>.*)\/.*\\.zip"
17+
],
18+
"datasourceTemplate": "github-releases"
19+
}
520
]
621
}

‎vocabulary

-1
This file was deleted.

0 commit comments

Comments
 (0)
Please sign in to comment.