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

[WFCORE-3932]: Adding support for standalone to standalone model synchronization / model difference computation #88

Closed
wants to merge 1 commit into from

Conversation

ehsavoie
Copy link
Contributor

@aloubyansky
Copy link
Contributor

From Galleon and provisioning perspective and roadmap the described functionality is a highly critical one that we need, ASAP. Thanks.

@kabir
Copy link
Contributor

kabir commented Jun 19, 2018

@ehsavoie Can you please add in the new Community Documentation section I just mentioned on wildfly-dev?

@rjanik114
Copy link

@kabir can we get an EAP7 planning issue for this?
@ehsavoie I have a question about the requirements in the proposal. In hard requirements you write that this should target the complete model, including deployments. In non-requirements, there's written that files (including deployments) are not targeted. IIUC, this means that the result of the diff will contain the information about what was deployed, but not the actual deployment files?

@ehsavoie
Copy link
Contributor Author

@LittleJohnII yes you are correct, Galleon provides already the filesystem changes so those files are already available. In a could environment I guess the deployment files would me mounted shared filesystem or whatever thus only the information about which files we are going to use is pertinent.

…hronization / model difference computation
@aloubyansky
Copy link
Contributor

Reabsed (had to fix the build) commit is aloubyansky/wildfly-core@426251a

@ehsavoie ehsavoie closed this Jul 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants