Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create define for patching JBoss/WildFly #86

Open
cardil opened this issue Jun 29, 2016 · 0 comments
Open

Create define for patching JBoss/WildFly #86

cardil opened this issue Jun 29, 2016 · 0 comments

Comments

@cardil
Copy link
Collaborator

cardil commented Jun 29, 2016

Design

There should be a define that could patch and rollback JBoss and WildFly with Red Hat provided ZIP patches via HTTP/S or local files.

Examples:

Apply with HTTP downloading

jboss::patch { 'jboss-eap-6.4.8':
  ensure  => 'applied', # supporting also present, absent, rollbacked
  uri     => 'https://proxy.localdomain/redhat/jboss-eap/patches/6.4/jboss-eap-6.4.8-patch.zip',
  product => 'jboss-eap',
  version => '6.4.8',
}

Apply with local file

jboss::patch { 'jboss-eap-6.4.8':
  ensure => 'applied',
  uri    => 'file:///usr/src/jboss-eap-6.4.8-patch.zip',
}

Apply with puppet://

jboss::patch { 'jboss-eap-6.4.8':
  ensure => 'applied',
  uri    => 'puppet:///module/appserver/patches/jboss-eap-6.4.8-patch.zip',
}

Rollback specific version

jboss::patch { 'jboss-eap-6.4.8':
  ensure  => 'rollbacked',
  product => 'jboss-eap',
  version => '6.4.8',
}

Scope of change

  1. New manifest
  2. New backing type and provider
  3. Unit tests with rspec for backing type and provider Ruby code
  4. Integration tests with puppet-rspec for manifest
  5. Acceptance tests with beaker
  6. Documentation on README.md
  7. Documentation on Wiki GH pages

More info

@cardil cardil added the feature label Jun 29, 2016
@cardil cardil added this to the v2.0.0 - CitrusAngel milestone Jun 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant