Skip to content

Preserve context case in macro names - #349

Merged
pederhan merged 2 commits into
unioslo:masterfrom
JonasQuin42:fix-context-macro-case
Oct 22, 2026
Merged

pederhan merged 2 commits into
unioslo:masterfrom
JonasQuin42:fix-context-macro-case

Conversation

@JonasQuin42

@JonasQuin42 JonasQuin42 commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

Context macros were getting uppercased as a whole, so something like {$VFS.FS.PUSED.MAX.CRIT:"/var/log"} turned into {$VFS.FS.PUSED.MAX.CRIT:"/VAR/LOG"} and the macro commands went looking for a macro that doesn't exist. Zabbix treats the context as case sensitive, so now only the part before the first : gets uppercased.

Added a few context cases to the existing fmt_macro_name test.

@JonasQuin42

Copy link
Copy Markdown
Contributor Author

Bump. Same deal as #348, CI runs expired waiting on approval rather than failing. Small fix, macros with an uppercase context like {$FOO:"Bar"} get lowercased on create/update so they stop matching what's on the host.

@pederhan pederhan 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.

Thank you for catching this!

@pederhan
pederhan merged commit 9424878 into unioslo:master Oct 22, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants