Project

General

Custom queries

Profile

Actions
Copy link

Bug #34328

closed

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

GraphQL is using Setting model directly

Added by Ondřej Ezr about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ondřej Ezr
Category:
Settings
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/9066
Fixed in Releases:
3.3.0
Found in Releases:
Red Hat JIRA:

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 1 (0 open — 1 closed)

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

Updated by Ondřej Ezr about 3 years ago

  • Parent task set to #29939
#2

Updated by The Foreman Bot about 3 years ago

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

Updated by The Foreman Bot about 3 years ago

  • Fixed in Releases 3.3.0 added
#4

Updated by Ondřej Ezr about 3 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF