-
-
Notifications
You must be signed in to change notification settings - Fork 94
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
Assign rule regex seems incorrect #209
Comments
I do something quite similar and it works for me with module v1.0.1.
But I also test with 'host.vars.os' and it works, no regex problems.
Best Regards |
Did you really use assign => ['host.var.os'], that looks like you forgot the 's' at the end of 'vars'? Of course, the error message doesn't help. |
Can you also test the current master? #208 should be fixed there |
I think the short var is a typo from my adjustment after the paste. It looks like my fork is missing a few commits. I'll rebase and test again. |
I've rebased now and I look to be having a new error, so perhaps I opened this too soon. Thanks for the advice. I'll close this out and reopen if I see this issue again. |
Hi. I'm starting to migrate to this module, and I'm trying to apply a service that looks like the following.
The assign target fails with the following error:
From my reading of the docs, and prior working with icinga2, the assign rule above should be valid. My goal is to assign this notification to a host where the os variable exists, no matter its value. Perhaps there is a better approach to this. Not all hosts have the os variable, since I might be monitoring external systems that don't run puppet, for example.
Is there a simple workaround, or does the regex need updating? Any advice here would be appreciated.
The text was updated successfully, but these errors were encountered: