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: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -116,21 +116,21 @@ Preparing stack JSON...
116
116
Creating stack mystack...
117
117
```
118
118
119
-
Verbose mode can be enabled through [VERBOSE_MODE envvar](#with-envvars) or [-v flag](with-flags).
119
+
Verbose mode can be enabled through [VERBOSE_MODE envvar](#with-envvars) or [-v flag](#with-flags).
120
120
121
121
### Debug mode
122
122
123
123
In debug mode the script prints as much information as possible to help diagnosing a malfunction.
124
124
125
125
**WARNING**: Debug mode will print configuration values (with Portainer credentials) and Portainer API responses (with sensitive information like authentication token and stacks environment variables). Avoid using debug mode in CI/CD pipelines, as pipeline logs are usually recorded.
126
126
127
-
Debug mode can be enabled through [DEBUG_MODE envvar](#with-envvars) or [-d flag](with-flags).
127
+
Debug mode can be enabled through [DEBUG_MODE envvar](#with-envvars) or [-d flag](#with-flags).
128
128
129
129
### Strict mode
130
130
131
131
In strict mode the script never updates an existent stack nor removes an unexistent one, and instead exits with an error.
132
132
133
-
Strict mode can be enabled through [STRICT_MODE envvar](#with-envvars) or [-t flag](with-flags).
133
+
Strict mode can be enabled through [STRICT_MODE envvar](#with-envvars) or [-t flag](#with-flags).
0 commit comments