Sunsetting foreman_cockpit

With cockpit integration into remote execution on the horizon and the old cockpit plugin lacking a release to make it compatible again, I think it is time for sunsetting the plugin officially, so everyone is aware of. I have seen too many people asking for the compatibility release or wondering that the plugin does not work. I can not do the sunsetting / releasing but depending on your opinion I will try to move this topic forward.

  • Sunset foreman_cockpit when integration in REX is ready
  • Sunset foreman_cockpit now

0 voters

  • Release foreman_cockpit 2.0.1before sunsetting
  • No more release

0 voters

If you see other options, please comment.

Any more opinions? Only 4 including myself and even split does not help me with the decision how to progress. :wink:

I would be happy if someone does another release just to allow users to upgrade and cleanly remove it, but looks like it’s been a couple of years since 2.0.3 came out and it might be too much effort to get it working with current foreman.
So, as I don’t see anyone stepping up to make it compatible, I suggest setting the right expectations and marking it as unsupported. Luckily, it has no db migrations so removal should be quite straightforward.

1 Like

I created the following pull requests.

Plugin itself:

Documentation on the homepage:

puppet-foreman:

foreman-installer:

Is another removal required I did not think about?
Should the packages be removed? If yes, how to do this?

1 Like