[dev.icinga.com #13513] Rework default order values for all objects

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/13513

Created by lbetz on 2016-12-10 11:27:18 +00:00

Assignee: (none)
Status: Closed (closed on 2016-12-15 09:26:17 +00:00)
Target Version: v0.7.0
Last Update: 2016-12-15 09:26:17 +00:00 (in Redmine)

---

How should be the defaut order of config objects in the target file?

[icinga-migration]

Updated by lbetz on 2016-12-10 11:33:11 +00:00

• CheckCommand
• Endpoint
• Zone
• Host
• Service

templates always before real objects

[icinga-migration]

Updated by bsheqa on 2016-12-12 07:48:11 +00:00

Sounds good to me

[icinga-migration]

Updated by lbetz on 2016-12-12 16:16:37 +00:00

But the list isn't complete? What's with the other object types?

[icinga-migration]

Updated by bsheqa on 2016-12-13 12:36:26 +00:00

Heres my suggestion:

• CheckCommand
• EventCommand
• NotificationCommand
• TimePeriod
• Endpoint
• Zone
• ApiUser
• Host
• HostGroup
• Service
• ServiceGroup
• Dependency
• User
• UserGroup
• Notification
• ScheduledDowntime
• CompatLogger
• CheckresultReader

[icinga-migration]

Updated by bsheqa on 2016-12-14 12:31:32 +00:00

I implemented the follwing order now:

5 - CompatLogger 
10 - CheckresultReader
15 - CheckCommand
20 - EventCommand
25 - NotificationCommand
30 - ApiUser
35 - TimePeriod
40 - Endpoint
45 - Zone
50 - Host
55 - HostGroup
60 - Service
65 - ServiceGroup
70 - Dependency
75 - User
80 - UserGroup
85 - Notification
90 - ScheduledDowntime

https://github.com/Icinga/puppet-icinga2-rewrite/tree/feature/default-object-order-13513

[icinga-migration]

Updated by lbetz on 2016-12-14 21:50:12 +00:00

That sounds good. Maybe put a default 0 to the custom config fragment.

[icinga-migration]

Updated by bsheqa on 2016-12-15 09:26:17 +00:00

• Status changed from Feedback to Closed
• Done % changed from 0 to 100