Feature #35375: db:seed should run on every upgrade even if there are no changes to seed files directly - Foreman

Actions

Feature #35375

closed

db:seed should run on every upgrade even if there are no changes to seed files directly

Added by Samir Jha almost 4 years ago. Updated 5 months ago.

Status:

Closed

Priority:

Normal

Assignee:

Bernhard Suttner

Category:

-

Target version:

-

Difficulty:

Triaged:

No

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman/pull/10858

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Today the foreman_seeder.rb : https://github.com/theforeman/foreman/blob/c3c697fa131aa54c11918bcc563a7789f3c08ef7/app/services/foreman_seeder.rb#L40
checks if any seed files have changed to run/skip seeding. This is not ideal as any changes to helper methods are not considered when deciding whether to run/skip seeding.

We should probably delete the Foreman.internal record pre-upgrade to make sure db:seed runs during all upgrades.

Actions

Also available in: Atom PDF