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 #12952] Add possibility to enabled/disable objects via REST API #504

Open
icinga-migration opened this issue Oct 21, 2016 · 4 comments

Comments

@icinga-migration
Copy link

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

Created by tobiasvdk on 2016-10-21 10:10:05 +00:00

Assignee: (none)
Status: New
Target Version: 1.3.1
Last Update: 2016-11-30 09:04:03 +00:00 (in Redmine)


Currently it's not possible to enable/disable an object via the REST API. Also this state is not displayed when GETting an object from icinga director.

Getting the status could look like:

{'object_name': 'my-host.domain',
 'object_type': 'object',
 'object_disabled': False}

Or if multiple status are possible / should be possible in future:

{'object_name': 'my-host.domain',
 'object_type': 'object',
 'object_status': 'enabled'}
@icinga-migration
Copy link
Author

Updated by tgelf on 2016-10-21 16:37:25 +00:00

Property name is "disabled", modifying it works fine for me. However, it's missing when GETting it, that's true - thanks for reporting this.

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-10-24 03:57:34 +00:00

  • Target Version set to 1.2.0

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-11-03 12:43:01 +00:00

  • Target Version changed from 1.2.0 to 1.3.0

@icinga-migration
Copy link
Author

Updated by tgelf on 2016-11-30 09:04:03 +00:00

  • Target Version changed from 1.3.0 to 1.3.1

@icinga-migration icinga-migration added this to the 1.3.1 milestone Jan 17, 2017
@Thomas-Gelf Thomas-Gelf removed this from the 1.3.1 milestone Feb 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants