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 #10923] API actions: Decide whether fixed: false is the right default #3812

Closed
icinga-migration opened this issue Jan 4, 2016 · 5 comments
Labels
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Jan 4, 2016

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

Created by jflach on 2016-01-04 11:32:39 +00:00

Assignee: jflach
Status: Resolved (closed on 2016-02-08 15:20:04 +00:00)
Target Version: 2.4.2
Last Update: 2016-02-23 09:58:37 +00:00 (in Redmine)

Icinga Version: 2.5.0
Backport?: Already backported
Include in Changelog: 1

When writing the config of a ScheduledDowntime it is assumed to be fixed:

fixed   Optional. Whether this is a fixed downtime. Defaults to true.

In the action schedule-downtime the default is false:

fixed   boolean     Optional. Defaults to false. If true the downtime is fixed otherwise flexible. See downtimes for more information.

It is to discuss whether it is a good idea to have different defaults.

Changesets

2016-02-08 15:04:41 +00:00 by jflach 964cfce

Make schedule-downtime default fixed

fixes #10923

2016-02-23 08:43:53 +00:00 by jflach 9bc7f0a

Make schedule-downtime default fixed

fixes #10923
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jan 11, 2016

Updated by mfriedrich on 2016-01-11 09:43:08 +00:00

Fixed should be enabled by default imho.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Jan 29, 2016

Updated by mfriedrich on 2016-01-29 09:36:47 +00:00

  • Category changed from ITL to API
  • Status changed from New to Assigned
  • Assigned to set to jflach

@jean

Please change the API actions default.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Feb 8, 2016

Updated by jflach on 2016-02-08 15:20:04 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset 964cfce.

@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Feb 8, 2016

Updated by jflach on 2016-02-08 15:24:38 +00:00

  • Target Version set to 2.4.2
@icinga-migration
Copy link
Member Author

@icinga-migration icinga-migration commented Feb 23, 2016

Updated by gbeutner on 2016-02-23 09:58:37 +00:00

  • Backport? changed from Not yet backported to Already backported
@icinga-migration icinga-migration added this to the 2.4.2 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.