Add support for WildFly configuration snapshots and rollback mechanism #291
Description
SUMMARY
Currently, the wildfly_install role is responsible for installing and configuring WildFly, while the wildfly_uninstall role is used for full uninstallation. However, when configuration changes applied by our roles fail, the WildFly instance may end up in a non-functional state. In such cases, manual intervention is required to identify and fix the problem, leaving the instance unavailable in the meantime.
To improve this, we propose implementing a mechanism to take configuration snapshots using the :take-snapshot operation available via the JBoss CLI for standalone mode, as documented in the Red Hat EAP 7.4 Management CLI Guide. This would allow us to:
-
Take a snapshot before applying any configuration changes.
-
Roll back to the last known good state in case of failure using the snapshot mechanism.
We can either create a new role (e.g., wildfly_snapshot) or enhance the existing wildfly_utils role to include:
-
Snapshot creation via CLI (:take-snapshot)
-
Conditional rollback on failure
Before implementing, we need to:
- Test and verify how the snapshot and restore mechanism behaves when the YAML configuration extension is enabled.
ISSUE TYPE
- Feature Idea