You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to use native Java gateway to JBoss CLI instead of spawning command line processes separately. In theory this should greatly increase the speed of evaluating the catalog.
puppet class jboss::plugins::rjb that will be included by default, and will install rjb gem into system (should be compatibile w Puppet OSS and Enterprise)
abstract provider code changes, implementing 2 strategies: process, rjb and using rjb if it is available and not specified explicitly by user.
unit and acceptance tests
After dropping support for Puppet 2.x, provider code can use features for providers
The text was updated successfully, but these errors were encountered:
The idea is to use native Java gateway to JBoss CLI instead of spawning command line processes separately. In theory this should greatly increase the speed of evaluating the catalog.
Example of using command line API here: https://developer.jboss.org/wiki/JBossAS7Command-linePublicAPI
RJB Homepage: http://www.artonx.org/collabo/backyard/?RubyJavaBridge
Sample Ruby code (will be delivered):
Scope of change:
jboss::plugins::rjb
that will be included by default, and will installrjb
gem into system (should be compatibile w Puppet OSS and Enterprise)process
,rjb
and usingrjb
if it is available and not specified explicitly by user.After dropping support for Puppet 2.x, provider code can use
features
for providersThe text was updated successfully, but these errors were encountered: