Project

General

Profile

Bug #34328

Tracker #29939: Improve setting definition DSL and move setting registry to memory

GraphQL is using Setting model directly

Added by Ondřej Ezr 5 months ago. Updated 4 months ago.

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

Description

GraphQL is using Setting model and database directly, but it needs to go through the registry to continue to work as expected (getting the correct values on read and write correctly)


Subtasks

Refactor #34335: Make GraphQL read settings from RegistryRejectedOndřej Ezr

Associated revisions

Revision 09414bf0 (diff)
Added by Ondřej Ezr 4 months ago

Fixes #34328 - GraphQL use directly SettingRegistry

GraphQL was reading the settings from DB, but now we have the registry, it needs to read it from there instead.

Mutation needs to set the value through the SettingRegistry as well.

History

#1 Updated by Ondřej Ezr 5 months ago

  • Parent task set to #29939

#2 Updated by The Foreman Bot 5 months ago

  • Assignee set to Ondřej Ezr
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/9066 added

#3 Updated by The Foreman Bot 4 months ago

  • Fixed in Releases 3.3.0 added

#4 Updated by Ondřej Ezr 4 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF