Skip to content
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 #13070] Validate and activate config package stages without triggering a reload #4769

Closed
icinga-migration opened this issue Nov 8, 2016 · 3 comments
Labels
area/api REST API enhancement New feature or request
Milestone

Comments

@icinga-migration
Copy link

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

Created by tgelf on 2016-11-08 10:54:09 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-11-08 10:54:09 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

When I currently deploy a new stage to a config package, Icinga immediately performs validation, switches the active stage and reloads itself. I'd like to have something like a boolean 'reload' flag which should default to true. Setting this to false should still validate the config and switch the stage name, but do not reload yet. This would allow to prepare a configuration for later deployment and to make sure that config after a planned or unplanned restart would reflect what live modification changed on our objects.


Relations:

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-11-08 10:54:19 +00:00

  • Relates set to 13069

@icinga-migration icinga-migration added the enhancement New feature or request label Jan 17, 2017
@dnsmichi dnsmichi added this to the 2.8.0 milestone Sep 20, 2017
@dnsmichi dnsmichi added the area/api REST API label Sep 20, 2017
@dnsmichi
Copy link
Contributor

Amended doc and code style fixes. Thanks for the patch 👍

@dnsmichi
Copy link
Contributor

Ups. Wrong issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api REST API enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants