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

Add option to create host "disabled" #71

Closed
widhalmt opened this issue Jan 31, 2018 · 3 comments
Closed

Add option to create host "disabled" #71

widhalmt opened this issue Jan 31, 2018 · 3 comments
Assignees

Comments

@widhalmt
Copy link
Member

Hi,

Could you add an option to have new hosts added as "disabled" in Director? I have a customer who imports hosts during setup but wants to start monitoring after some extra steps are finished. Having the host from the start is a good thing so the monitoring admins can make changes, add templates, etc. but the host might not be ready for monitoring, yet.

Cheers,
Thomas

@LordHepipud
Copy link
Collaborator

Hello,

In general this would be possible with a simple argument, beeing passed as JSON to the host creation or by specifiying a custom JSON Object.
It depends however how the host is created.

If you are using the module with user / password - it would be no problem at all.
In case you are using the SelfService API from the Director, it will not be possible as the Director is not allowing this kind of argument and dropping the request. Furthermore it would not be possible to pass the argument properly.

So I see two steps here:

  • Include this feature into the PowerShell Module with an argument
  • Extend the IcingaDirector SelfService API with an option to create disabled host objects

Any further suggestions?

@widhalmt
Copy link
Member Author

widhalmt commented Feb 1, 2018

Since the setup which gave me the idea is using the self-service API a lot I'll open an according issue Director.

@LordHepipud
Copy link
Collaborator

As we are moving forward with Icinga for Windows and the PowerShell Framework, we will not continue on this issue.

@LordHepipud LordHepipud removed this from the v1.3.0 milestone Apr 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants