-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] folder creation always lowers the foldername #569
Comments
Hi @Mik3yZ, I would say works as intended. Folder title and path (folder name) are two different parameters. |
Hi @msekania Maybe my description was a bit off, changed it to reflect what i mean. Hope this makes thing clearer. |
So, to come back to your last sentence @msekania, |
lines 220-221: _normalize_path(...) is called with a parameter |
true, however it does set |
ansible-collection-checkmk.general/plugins/modules/folder.py Lines 223 to 224 in 300764e
states it explicitly what goes to
ansible-collection-checkmk.general/plugins/modules/folder.py Lines 481 to 485 in 300764e
|
yes, i saw that too. however i do get only lowercase names while creating the folders. i would then say line 220 needs to be changed from:
|
problem is somewhere else, because |
It should be I'll make corrections |
Describe the bug
When creating a folder with uppercase letters, the folder.py changes it to lowercase.
Component Name
Component Name: folder
Ansible Version
Checkmk Version and Edition
Checkmk Enterprise Edition 2.2.0p20
Collection Version
To Reproduce
Create a folder with:
Expected behavior
A folder named FolderName, with path /foldername
Actual behavior
A folder named foldername with path /foldername
Minimum reproduction example
See above
Additional context
folder.py
contains:ansible-collection-checkmk.general/plugins/modules/folder.py
Lines 220 to 221 in 300764e
And this function (
_normalize_path
) changes the string to lowercase:ansible-collection-checkmk.general/plugins/modules/folder.py
Lines 274 to 278 in 300764e
I would advise to not normalize the name / title as a path.
The text was updated successfully, but these errors were encountered: