Bug #9812
closed
'match' and 'value' parameters in override value's create should be required in apidoc
Added by Martin Bacovsky over 9 years ago.
Updated about 6 years ago.
Description
Currently it allows CLI to attempt to create override value without these params which result in 500.
[ INFO 2015-03-18 16:00:34 API] POST /api/smart_variables/205/override_values
[DEBUG 2015-03-18 16:00:34 API] Params: {
"override_value" => {}
}
[DEBUG 2015-03-18 16:00:34 API] Headers: {}
[DEBUG 2015-03-18 16:00:35 API] 500 Internal Server Error
{
"error" => {
"message" => "undefined method `match' for nil:NilClass"
}
}
Not only they should be required in the docs but we must make sure the api can cope with the missing parameters and not to fail with 500.
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2255 added
- Pull request deleted (
)
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Assignee set to Shlomi Zadok
- Translation missing: en.field_release set to 35
- Related to Bug #10528: Can't save a smart class parameter/smart variable with the value 'false' added
- Related to Bug #9187: Overrideable empty puppet class parameters are still validate their default value added
- Related to Bug #11663: Empty lookup value validated even when use_puppet_default is checked added
Also available in: Atom
PDF