Seed may not be triggered after migration
In puppet-foreman we rely on a transitive notification from foreman::rake db:migrate via foreman_config_entry db_pending_seed to foreman::rake db:seed. In #34161 we've seen that this isn't always true. An explicit notification would be better.
Fixes #34308 - Explicitly notify db:seed from db:migrate
This is similar to a293e0084d3c2d62c12ccc6a13338b5db01fe8cf and the
problem is that a transitive notify doesn't always happen. However, if
a db:migrate happens a db:seed should always happen. So his may be a
redundant specification, but it's better to be explicit than relying on
#3 Updated by Ewoud Kohl van Wijngaarden 4 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman|d86ea26f7ac50cd708c17b9333a88f1bbadbf3d9.