Project

General

Profile

Bug #28929

settings api accept different values than what it returns

Added by Simon Peeters 10 months ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
API
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

The settings api endpoint returns nicely typed settings: the get request returns arrays, hashes, integers and strings depending on the type of the setting.
When writing to the api endpoint however, the api only accepts string input, this makes it hard to properly ensure the state of a setting (trough for example puppet)

Associated revisions

Revision e7196da2 (diff)
Added by Simon Peeters 10 months ago

Fixes #28929 - allow complex types in settings api

Previously the settings api only accepted stringified forms of complex
settings values, while returning the correctly typed ones.

This change allows setting both stringified and non stringified forms.

History

#2 Updated by The Foreman Bot 10 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/7430 added

#3 Updated by The Foreman Bot 10 months ago

  • Fixed in Releases 2.0.0 added

#4 Updated by Anonymous 10 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF