Skip to content

Commit 26b9659

Browse files
authored
Update safe-upgrade-practices.md
1 parent 2ef10d6 commit 26b9659

File tree

1 file changed

+45
-0
lines changed

1 file changed

+45
-0
lines changed

articles/operator-service-manager/safe-upgrade-practices.md

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -237,3 +237,48 @@ To enable the SkipUpgrade feature via `roleOverrideValues`, refer to the followi
237237
- The `skipUpgrade` flag is enabled. If the upgrade request for `hellotest` meets the precheck criteria, the upgrade is skipped.
238238
- **nfApplication: `runnerTest`**
239239
- The `skipUpgrade` flag isn't specified. Therefore, `runnerTest` executes a traditional Helm upgrade at the cluster level, even if the precheck criteria are met.
240+
241+
242+
243+
## Complete roleOverrideValues option reference
244+
Bringing together all prior examples in this article, as well as examples in other articles, the below reference provides all presently supported install and upgrade options which can be set through the `roleOverrideValues` mechanism.
245+
246+
```json
247+
{
248+
"roleOverrideValues": [
249+
{
250+
"name": "nfApplication1",
251+
"deployParametersMappingRuleProfile": {
252+
"helmMappingRuleProfile": {
253+
"options": {
254+
"nfConfiguration": {
255+
"rollbackEnabled": "true"
256+
},
257+
"installOptions": {
258+
"atomic": "true",
259+
"wait": "true",
260+
"timeout": "1",
261+
"testOptions": {
262+
"enable": "true",
263+
"timeout": "true",
264+
"rollbackOnTestFailure": "true",
265+
"filter": [
266+
"test1",
267+
"test2"
268+
]
269+
}
270+
},
271+
"upgradeOptions": {
272+
"atomic": "true",
273+
"wait": "true",
274+
"timeout": "1",
275+
"skipUpgrade": "true",
276+
"testOptions": {
277+
"enable": "true",
278+
"timeout": "true",
279+
"rollbackOnTestFailure": "true",
280+
"filter": [
281+
"test1",
282+
"test2"
283+
] } } } } } } ] }
284+
```

0 commit comments

Comments
 (0)