Subscription detail blank

Support
,
9

You can see our progress here: https://github.com/theforeman/foreman-packaging/pull/3012

The rough idea is:

  • When we build Foreman, we generate RPM Provides that list webpack assets the plugins can reuse. This includes a hash of the asset file.
  • When we build a plugin, we generate RPM Requires that list the used webpack assets and their hashes.
  • Now if Foremans assets change (and thus the hash), the plugin RPMs become uninstallable which is an indicator for us to rebuild them.

Certainly not optimal, but at least we now have a asset-related relationship between Foreman and the plugins that can be acted upon.

1 Like