Project

General

Profile

Refactor #33906

Drop the fix_db_cache setting

Added by Tomer Brisker about 1 year ago. Updated 7 months ago.

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

Description

This setting was added to handle some migrations back in 2014 and isn't really used anywhere else. We can safely drop it.

Associated revisions

Revision 46e6b1ef (diff)
Added by Tomer Brisker about 1 year ago

Fixes #33906 - Drop fix_db_cache setting

This setting was introduced when the current permissions model was
introduced in Foreman 1.7 to allow recreating the user permissions cache
after the migration from the previous model. The setting has no other
uses.
If a user wants to manually recreate the permissions cache for some
reason, the rake task remains available, but it is no longer
programattically executed.
The migration converting the premissions from the old model to the new
one has been emptied, on a new install there will not be any permissions
in the old model and any upgrades will have already executed this
migration by now.

History

#1 Updated by Tomer Brisker about 1 year ago

  • Assignee set to Tomer Brisker
  • Status changed from New to Assigned

#2 Updated by The Foreman Bot about 1 year ago

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

#3 Updated by The Foreman Bot about 1 year ago

  • Fixed in Releases 3.1.1 added

#4 Updated by Ondřej Ezr about 1 year ago

  • Fixed in Releases 3.2.0 added
  • Fixed in Releases deleted (3.1.1)

#5 Updated by Tomer Brisker about 1 year ago

  • Status changed from Ready For Testing to Closed

#6 Updated by Amit Upadhye 7 months ago

  • Subject changed from drop fix_db_cache setting to Drop the fix_db_cache setting

Also available in: Atom PDF