puppet-wildfly
puppet-wildfly copied to clipboard
voxpupuli
Puppet module to install, configure and manage Wildfly (8/9/10+), JBoss EAP (6.1+/7.0+) and some Wildfly based products like apiman, Keycloak and Infinispan.
Hi, I am running into a problem adding a jgroup configuration after initial installation/configuration. I am using the module version 2.0.2 for configuration management, so i add the wildfly::resource manually...
Hi, I'm currently trying to use this module to configure ActiveMQ for WildFly 10.1 but I'm running into some trouble and I'm not sure what I'm doing wrong. Essentially we...
Right now deployments are 'managed' deployments by default. In order to support 'unmanaged' deployments, there should be the option to add `--unmanaged` as a parameter to the `deploy` cli command....
Hi, Looking at the issues list I've encountered the issue where the KeycloakDS datasource can't be changed because of the expression on the jdbc URL. Trying to bypass this issue,...
The [code](https://github.com/biemond/biemond-wildfly/blob/a5b3eda7f6ac3fd0d527786c0290c174ac2d81ab/lib/puppet_x/wildfly/api_client.rb#L28) designed to retry api connections if Wildfly hasn't started up yet isn't working for me. ``` Error: /Stage[main]/Profile::Keycloak/Wildfly::Resource[/socket-binding-group=standard-sockets/socket-binding=proxy-https]/Wildfly_resource[/socket-binding-group=standard-sockets/socket-binding=proxy-https]: Could not evaluate: 757: unexpected token at 'Error503 - Service...
Hi When I try to update the default keycloak standalone-ha database, the code explodes when trying to compare the `is` and `should` values. ```puppet wildfly::datasources::datasource { 'KeycloakDS': config => {...
It appears that enabling AJP is not consistent between JBoss EAP 6.x and 7.x. In 6.x, this works: ``` class { 'wildfly': distribution => 'jboss-eap', init_system => 'systemd', version =>...
Wildfly has a detyped management API to manipulate Management Model that wildscribe.github.io uses to generate a documentation, but we could use to generate defined types for specific versions, for example:...
Some default values should vary based on **distribution:version**: `user`, `group`, `dirname` and `console_log` not only config and service related data. Examples for EAP 6/7 in the README express this scenario.
Example: ` /subsystem=ee:write-attribute(name=global-modules, value=[{ name=>'org.postgresql', slot=>'main'}])`