Project

General

Profile

Bug #33626

Allow foreman plugins to use webpack

Added by Bernhard Suttner 4 months ago. Updated 2 months ago.

Status:
Closed
Priority:
Normal
Category:
Plugin integration
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Currently, webpack for js does only handle directories for plugins which
- start with foreman or katello
- don't end with core

It should be possible to specify in a plugin directly, if they should be handled by plugin_webpack_directories.rb or not.

Associated revisions

Revision 4cc19f6c (diff)
Added by Bernhard Suttner 3 months ago

Fixes #33626 - use webpack for foreman plugin gems

A plugin can specify by the following line in the gemspec that it is
really a foreman plugin:

s.metadata = { "is_foreman_plugin" => "true" }

History

#1 Updated by The Foreman Bot 4 months ago

  • Assignee set to Bernhard Suttner
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/8810 added

#2 Updated by The Foreman Bot 3 months ago

  • Fixed in Releases 3.1.0 added

#3 Updated by Anonymous 3 months ago

  • Status changed from Ready For Testing to Closed

#4 Updated by Amit Upadhye 2 months ago

  • Category set to Plugin integration

Also available in: Atom PDF