-
Notifications
You must be signed in to change notification settings - Fork 48
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] Since version 2.1.0p5 modules not working anymore #78
Comments
Sure this only happens since p5? I did change the path handling in p4. I also just checked the tests I added and found that I generate paths in a loop. So to get "/Blub/Baa" I first create "/Blub" and then "/Blub/Baa". The error also says that the REST API only wants to create the last folder given. Or in other words. This behaves like |
Yea I have tested it with p4 and there it worked. And yes it creates like „mkdir“ because „mkdir -p“ was not working in the beginning.. but I don’t understand what this has to do with the problem?! |
The error message you have written says that the parent folder |
Ok.. I have copied the module and fixed it locally by myself anyway. So just take it as notice and do what you think is ok.. The parent folder is already existing and its folder ID (not title!) is: The |
Btw.. and just fyi - I also fixed the host module which was not working anymore. The API Maybe was sending not the first OLD:
NEW:
|
@elwood218 your issue should be fixed with #147. It will be included in version |
Closing this due to staleness, as there is another fix in 993b4ce. If there is anything else, please open a new issue. |
Describe the bug
Folders cannot be created because of changes in the API since 2.1.0p5
Component Name
folder
, maybe alsohost
Ansible Version
Checkmk Version
2.1.0p5 (CEE) and 2.1.0p6
Collection Version
Environment
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Actual behavior
Screenshots
Additional context
Please remove the
.lower()
in following line on folder.py. Please also check host.py.The text was updated successfully, but these errors were encountered: