Added new way of configuration. #1560
Conversation
|  | ||
|  | ||
|  |
There was a problem hiding this comment.
Please include the images as files in the git repository as part of this PR.
We store images in the .gitbook/assets directory, so that they are versioned and accessible for Gitbook to use. I doubt it will work with images stored simply as user-attachments on github and we don't want to risk Github cleaning them up after a while.
There was a problem hiding this comment.
Seems I don't have access to push. Attaching zip files contain 6 images.
remote: Permission to StackVista/stackstate-docs.git denied to amolkharche13.
|
|
||
| **Troubleshooting**:- | ||
| 1) If you encounter an error message when clicking the ▶️ TEST button, check the logs on your SMTP server, typically located under `/var/log/mail.log`. You should find some clues to help resolve the issue. |
There was a problem hiding this comment.
To get a nice consistent layout with the rest of the docs you can simply use 1. to get a Markdown list. We don't number anything in the docs like this with 1).
Another option would be to give each case a level-3 header, but it may be hard to come up with short titles.
| When the username and password cannot be provided in the values but should come from an external secret, follow [these steps](/setup/security/external-secrets.md#getting-username-and-password-for-email-sending-from-an-external-secret) | ||
|
|
||
| To apply the changes, use the command: helm upgrade by passing --values values.yaml, |
There was a problem hiding this comment.
You now put this text into the ### Using an external secret section (probably happened with the conflict resolution). You probably want to have this right above that header.
|
|
||
|
|
||
| **Troubleshooting**:- |
There was a problem hiding this comment.
Instead of a bold text I would make this a level 2 header: ## Troubleshooting.
No description provided.