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 #10959] Better explaination for array values in "disk" CheckCommand docs #3833

Closed
icinga-migration opened this issue Jan 12, 2016 · 3 comments
Milestone

Comments

@icinga-migration
Copy link
Member

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

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

Created by mfriedrich on 2016-01-12 21:56:09 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2016-01-13 15:55:05 +00:00)
Target Version: 2.4.2
Last Update: 2016-02-23 09:58:39 +00:00 (in Redmine)

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

"Disk" command arguments which can be repeated provide misleading hints - it should clearly tell that either a single value or an array can be used. This probably affects other ITL commands.

http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/plugin-check-commands#plugin-check-command-disk

Changesets

2016-01-13 15:51:47 +00:00 by mfriedrich a9d09e4

Better explaination for array values in "disk" CheckCommand docs

fixes #10959

2016-02-23 10:41:04 +00:00 by (unknown) 0fc42e7

Update documentation

refs #10959
@icinga-migration
Copy link
Member Author

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

Updated by mfriedrich on 2016-01-13 15:55:05 +00:00

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

Applied in changeset a9d09e4.

@icinga-migration
Copy link
Member Author

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

Updated by mfriedrich on 2016-01-13 15:57:37 +00:00

  • Assigned to set to mfriedrich
@icinga-migration
Copy link
Member Author

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

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

  • Backport? changed from Not yet backported to Already backported
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.