Hi all-- I've submitted a PR <https://github.com/ansible/ansible/pull/26379> that contains enhancements to the JBoss module that have been kicked around in the JBoss/Ansible community (there are dozens of us!!). If someone can take a look and give me some feedback, I'd be most grateful. Ansible has the potential to help a lot of JBoss shops that want to tighten up their development cycle but aren't ready to drink the DevOps kool-aid yet. In order to unlock that potential, we need more features in the JBoss module.
At this juncture, the JBoss module only supports deployment/undeployment via the filesystem using the deployment scanner (a JBoss service that scans a particular fs directory for deployable files and deploys them). This means it either adds or removes a deployment artifact (e.g., a .war file) to a specified deployment directory. In older versions of JBoss, this was the only way to do hot deployments, but starting with JBoss 7, users have the option of using a provided CLI as well as an HTTP interface in addition to the fs method. The fs method is not recommended for production use. So as a first step towards enhancing the JBoss module, I've added support for deploying via the HTTP API and the CLI. Some of us have also talked about a facts module, possibly using jolokia <https://jolokia.org/> to gather detailed data on JBoss environments. A jolokia module could also extend deployment capabilities to other Java environments, since it's not specific to JBoss. Thanks! -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
