You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assignee: (none)
Status: Resolved (closed on 2014-05-22 11:15:02 +00:00)
Target Version: 2.0 Beta 1
Last Update: 2014-05-22 11:15:02 +00:00 (in Redmine)
Icinga Version: 0.0.8
We need a defined config file parse order for all kinds of recursive includes. Constants are for example not available everywhere but only "after" they have been defined. There have to be strict rules for this "after". Someone archiving and restoring a configuration wants to feel confident that what used to work will continue to do so.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/5854
Created by tgelf on 2014-03-25 16:27:13 +00:00
Assignee: (none)
Status: Resolved (closed on 2014-05-22 11:15:02 +00:00)
Target Version: 2.0 Beta 1
Last Update: 2014-05-22 11:15:02 +00:00 (in Redmine)
We need a defined config file parse order for all kinds of recursive includes. Constants are for example not available everywhere but only "after" they have been defined. There have to be strict rules for this "after". Someone archiving and restoring a configuration wants to feel confident that what used to work will continue to do so.
Cheers,
Thomas
Changesets
2014-05-19 18:44:35 +00:00 by (unknown) 41a4bfd
2014-05-19 18:56:32 +00:00 by (unknown) 3ef7c92
2014-05-19 19:17:04 +00:00 by (unknown) 3ad94c4
2014-05-22 10:40:39 +00:00 by (unknown) 0f79190
2014-05-22 11:12:58 +00:00 by gbeutner 46165db
Relations:
The text was updated successfully, but these errors were encountered: