The Director aims to be your new favourite Icinga config deployment tool. Director is designed for those who want to automate their configuration deployment and those who want to grant their “point & click” users easy access to the configuration.
Icinga Director should be able to update a variable object if the object has a null value and the value is already provided by Icinga Director for example in Service Template or Service Set.
Current Behavior
If previously the value for the variable object was given using Icinga2 REST API and we want to overwrite this value with the help of the Icinga Director, it is impossible.
Steps to Reproduce (for bugs)
With the help of Icinga2 REST API, I passed the value "13" for the postgres_critical variable.
Which resulted in overwriting the value that I had configured in "Icinga Service Sets"
I would like to reverse the process.
However, when I'm using the Icinga2 REST API to overite postgres_critical and put a null value for this variable.
curl -k -s -S -i -u user:pass -H 'Accept: application/json' -X POST 'https://localhost:5665/v1/objects/services/host-object!service-object -d '{ "attrs": { "vars.postgres_critical" : null }}'
It doesn't change anything.
I am unable to get back the value specified in Icinga Director.
The variable postgres_critical takes the value null
Inspect >> Executed Command >> '-c' ''
and does not retrieve the value previously configured in Icinga Director.
I can only see the Icinga Director value under original_attributes.
How to use a value defined in Icinga Director if previously this value was put under variable by Icinga2 REST API?
Your Environment
Director version 1.11.0
Icinga Web 2: 2.12.1
Icinga 2 version: r2.14.0-1
Operating System and version: Debian Linux 11 (bullseye)
Expected Behavior
Icinga Director should be able to update a variable object if the object has a null value and the value is already provided by Icinga Director for example in Service Template or Service Set.
Current Behavior
If previously the value for the variable object was given using Icinga2 REST API and we want to overwrite this value with the help of the Icinga Director, it is impossible.
Steps to Reproduce (for bugs)
With the help of Icinga2 REST API, I passed the value "13" for the postgres_critical variable. Which resulted in overwriting the value that I had configured in "Icinga Service Sets"
curl -k -s -S -i -u user:pass -H 'Accept: application/json' -X POST 'https://localhost:5665/v1/objects/services/host-object!service-object -d '{ "attrs": { "vars.postgres_critical" : "13" }}'
I would like to reverse the process. However, when I'm using the Icinga2 REST API to overite postgres_critical and put a null value for this variable. curl -k -s -S -i -u user:pass -H 'Accept: application/json' -X POST 'https://localhost:5665/v1/objects/services/host-object!service-object -d '{ "attrs": { "vars.postgres_critical" : null }}'
It doesn't change anything. I am unable to get back the value specified in Icinga Director. The variable postgres_critical takes the value null Inspect >> Executed Command >> '-c' '' and does not retrieve the value previously configured in Icinga Director.
I can only see the Icinga Director value under original_attributes.
How to use a value defined in Icinga Director if previously this value was put under variable by Icinga2 REST API?
Your Environment