Skip to content

Enhance password comment in config.example.yml - #1229

Merged
oxzi merged 1 commit into
Icinga:mainfrom
log1-c:patch-1
Nov 3, 2026
Merged

oxzi merged 1 commit into
Icinga:mainfrom
log1-c:patch-1

Conversation

@log1-c

@log1-c log1-c commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Updated comment for database password to include guidance on handling special characters.

Took me quite a while to figure out, because the resulting error when starting the service is not very helpful in that case

invalid configuration: invalid redis configuration: Redis host missing

@cla-bot cla-bot Bot added the cla/signed label Oct 30, 2026

@oxzi oxzi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for creating this PR.

I am unsure about having this comment in only one place when it addresses a limitation (or footgun) of YAML. How about putting the examples in single quotes instead? Or adding a general note at the top and/or in the docs?

@log1-c

log1-c commented Nov 2, 2026

Copy link
Copy Markdown
Contributor Author

How about putting the examples in single quotes instead?

Would have been too obvious 😅
I added the quotes and another hint in the config section

@log1-c
log1-c requested a review from oxzi November 2, 2026 08:48
@oxzi

oxzi commented Nov 2, 2026

Copy link
Copy Markdown
Member

I added the quotes and another hint in the config section

Thanks for the fast reply. However, I am still a bit unhappy about the change as it explicitly only handles database.password, while this is a general problem.

So, how about a warning note at the beginning of the docs - maybe after the last paragraph of the Configuration section before the Database Configuration subsection starts? I could imagine something like:

When using the YAML configuration, please be aware of how YAML handles strings. If your input field contains special characters - which is common for passwords -, enclose it in quotes.

This way, the information would be generic, as there are multiple potentially affected fields; even multiple password fields.

@oxzi oxzi added this to the 1.6.1 milestone Nov 3, 2026
@oxzi oxzi added the area/documentation Improvements or additions to documentation label Nov 3, 2026
@log1-c

log1-c commented Nov 3, 2026

Copy link
Copy Markdown
Contributor Author

Removed the previous hints and added a caution box at the beginning of the database configuration section.
Single quotes around the password in the config example still remain.

@oxzi oxzi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks again!

Please add yourself to the AUTHORS file and squash all your commits into one. Then, it's good for me :)

Comment thread doc/03-Configuration.md Resolved
@oxzi

oxzi commented Nov 3, 2026

Copy link
Copy Markdown
Member

Sorry @log1-c, but in my previous suggested changes leading > crept in :(

@log1-c

log1-c commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor Author

Please add yourself to the AUTHORS file

Is that mandatory? Because until now that was never requested.

and squash all your commits into one. Then, it's good for me :)

tbh, I have no idea how to do that. The Github interface does not seem to offer such an option.
I tried using the Github Copilot app, but it only did the squashing in my forked repo which did not seem to have an impact on the PR

Added note about wrapping password in single quotes for special characters.
@oxzi

oxzi commented Nov 3, 2026

Copy link
Copy Markdown
Member

Please add yourself to the AUTHORS file

Is that mandatory? Because until now that was never requested.

Depends. It is mostly there to acknowledge our contributors.

and squash all your commits into one. Then, it's good for me :)

tbh, I have no idea how to do that. The Github interface does not seem to offer such an option. I tried using the Github Copilot app, but it only did the squashing in my forked repo which did not seem to have an impact on the PR

No problem. I did it for you and force-pushed it to your PR branch.

@oxzi oxzi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks again and please excuse the back-and-forth here in the PR discussion.

@oxzi
oxzi enabled auto-merge November 3, 2026 09:39
@log1-c

log1-c commented Nov 3, 2026

Copy link
Copy Markdown
Contributor Author

Happy to help :)

Thanks again and please excuse the back-and-forth here in the PR discussion.

No worries, usual refinement process I'd say 👍

@oxzi
oxzi merged commit 7e56c01 into Icinga:main Nov 3, 2026
27 checks passed
@log1-c
log1-c deleted the patch-1 branch November 3, 2026 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/documentation Improvements or additions to documentation cla/signed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants