[dev.icinga.com #12350] Features

[icinga-migration]

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

Created by bsheqa on 2016-08-09 14:19:49 +00:00

Assignee: lbetz
Status: Closed (closed on 2016-09-12 13:04:26 +00:00)
Target Version: v0.3.0
Last Update: 2016-09-12 13:04:26 +00:00 (in Redmine)

---

A feature should call a defined resource ‘feature’. This defined resource handles the creation of the config file based on a dedicated template for each feature. All other steps required to fully enable a feature should be handled by the feature resource itself.

---

Relations:

• relates #12361
• relates #12365
• relates #12366

[icinga-migration]

Updated by bsheqa on 2016-09-06 07:38:20 +00:00

• Target Version changed from 313 to v0.3.0

[icinga-migration]

Updated by lbetz on 2016-09-08 11:04:04 +00:00

• Relates set to 12361

[icinga-migration]

Updated by lbetz on 2016-09-08 11:05:24 +00:00

• Relates set to 12365

[icinga-migration]

Updated by lbetz on 2016-09-08 11:05:40 +00:00

• Relates set to 12366

[icinga-migration]

Updated by lbetz on 2016-09-08 11:09:47 +00:00

• Assigned to set to lbetz

[icinga-migration]

Updated by lbetz on 2016-09-08 11:38:05 +00:00

• Done % changed from 0 to 100

Use of icinga2::config::file for resource ordering didn't work, because the file in features-available must not trigger a notify to the service if the feature is disabled.

[icinga-migration]

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

• Status changed from New to Closed