Bug #18989
open
When we set invalid values for api settings, we get an empty success response
Added by Nicolas CHARLES over 2 years ago.
Updated 15 days ago.
Description
On Rudder 6.2, maybe in previous versions as well
I was expecting an error
[root@server ~]# curl -k -X POST -H "X-API-TOKEN: $(cat /var/rudder/run/api-token)" 'http://localhost:8080/rudder/api/latest/settings' -d 'unexpected_unbound_var_values=sfg'
{"action":"modifySettings","result":"success","data":{"settings":{}}}
curl -k -X POST -H "X-API-TOKEN: $(cat /var/rudder/run/api-token)" 'http://localhost:8080/rudder/api/latest/settings' -d 'rudder_generation_delay=0DF'
{"action":"modifySettings","result":"success","data":{"settings":{}}}
- Target version changed from 6.2.3 to 6.2.4
- Target version changed from 6.2.4 to 6.2.5
- Target version changed from 6.2.5 to 6.2.6
- Target version changed from 6.2.6 to 6.2.7
- Target version changed from 6.2.7 to 6.2.8
- Target version changed from 6.2.8 to 6.2.9
- Target version changed from 6.2.9 to 6.2.10
- Target version changed from 6.2.10 to 6.2.11
- Target version changed from 6.2.11 to 6.2.12
- Target version changed from 6.2.12 to 6.2.13
- Target version changed from 6.2.13 to 6.2.14
- Target version changed from 6.2.14 to 6.2.15
- Target version changed from 6.2.15 to 6.2.16
- Target version changed from 6.2.16 to 6.2.17
- Target version changed from 6.2.17 to 997
- Target version changed from 997 to 6.2.18
- Target version changed from 6.2.18 to 6.2.19
- Target version changed from 6.2.19 to 6.2.20
- Target version changed from 6.2.20 to old 6.2 issues to relocate
- Subject changed from When we set invalid values fo api settings, we get an empty success response to When we set invalid values for api settings, we get an empty success response
- Regression set to No
- Target version changed from old 6.2 issues to relocate to 7.2.11
- Target version changed from 7.2.11 to 7.2.12
Also available in: Atom
PDF