Null values for ProbeConfiguration shouldn't be null in DB
Problem description
In the target_probe_agent.probe_configuration
, if a parameter is "removed" by a user, it should be undefined
in the webapp, and shouldn't appear in the JSON representation in the DBConf.
Environment
Panto versions
- Panto server version: 0.1.10
- Panto agent version: 0.1.10
- Panto web version: 0.1.10
Local environment
- Operating system: N/A
- Browser and version: N/A
Reproduction
- install a Probe on an Agent
- configure each parameter, even the optional
- save the configuration
- remove the value of the optional parameters
- check the DBConf, it should contain
null
s.
Expected behavior
{"address":"localhost"}
Observed behavior
{"address":"localhost","count":null,"interval":null,"timeout":null}
Edited by Charles Francoise