-
-
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
[dev.icinga.com #13035] Wrong syntax of "apply" in object.conf.erb template (afaik) #143
Comments
Updated by alorenzi on 2016-11-03 11:45:38 +00:00 |
Updated by bsheqa on 2016-11-08 10:22:13 +00:00
|
Updated by bsheqa on 2016-11-08 10:48:37 +00:00 Apply rules can be used in multiple ways. Generally an apply rule can target either a host or a service. Beside the described default way, there is also a configuration with 'apply for'. With that you can create a loop to apply objects based on a set of arrays or hashes combined with expressions. To cover all these cases, my solution would be this:
I would not differ service object types from other object types. Service apply rules can work without setting a target, but they also work with it. By setting the target for every object type we handle all types the same way and I like this better. Please give me feedback on this. I hope this would cover all cases in a "simple to use" way. |
Updated by bsheqa on 2016-11-08 10:52:34 +00:00
|
Updated by alorenzi on 2016-11-08 11:50:19 +00:00 Simple to use but hard to understand, i had to read a couple of times. :) Anyway, make sense. |
Updated by bsheqa on 2016-11-10 16:01:21 +00:00
|
Updated by alorenzi on 2016-11-10 16:18:46 +00:00 thanks :) |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/13035
Created by alorenzi on 2016-11-03 11:43:53 +00:00
Assignee: bsheqa
Status: Closed (closed on 2016-11-10 16:01:21 +00:00)
Target Version: v0.6.0
Last Update: 2016-11-10 16:18:46 +00:00 (in Redmine)
file: ./templates/object.conf.erb
at the moment it create a file like this:
should be
Relations:
The text was updated successfully, but these errors were encountered: