Bug 852161 - RFE: Ability to load scripts from various sources in CLI and RHQ server
RFE: Ability to load scripts from various sources in CLI and RHQ server
Status: CLOSED CURRENTRELEASE
Product: RHQ Project
Classification: Other
Component: CLI, Core Server (Show other bugs)
4.5
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: RHQ 4.5.0
Assigned To: Lukas Krejci
Mike Foley
:
Depends On:
Blocks: 852164
  Show dependency treegraph
 
Reported: 2012-08-27 14:02 EDT by Lukas Krejci
Modified: 2013-09-01 06:03 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-01 06:03:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lukas Krejci 2012-08-27 14:02:41 EDT
Description of problem:

Currently it is only possible to load additional scripts in the interactive CLI using the "exec -f" command.

This is insufficient not only because such approach provides very little modularity but also it restricts the possible location of the scripts to load to the local filesystem on the CLI deployment (and only in the interactive mode at that).

This means that such approach is unusable in the RHQ server, where alert scripts cannot take advantage of such (limited) ability.

We should provide a generic and extensible way of specifying the locations of scripts and loading them from such locations using the modular approach of given scripting language.
Comment 1 Lukas Krejci 2012-08-27 14:04:17 EDT
The list of currently implemented "script source providers" + a description of a way to provide a new implementation is provided on:
https://docs.jboss.org/author/display/RHQ/Script+Sources
Comment 2 Heiko W. Rupp 2013-09-01 06:03:24 EDT
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.

Note You need to log in before you can comment on or make changes to this bug.