We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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', }
README.md
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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
Apply with local file
Apply with puppet://
Rollback specific version
Scope of change
README.md
More info
The text was updated successfully, but these errors were encountered: