Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Exposing validate for general use #313

Closed
grtjn opened this issue Nov 21, 2014 · 2 comments
Closed

Exposing validate for general use #313

grtjn opened this issue Nov 21, 2014 · 2 comments

Comments

@grtjn
Copy link
Contributor

grtjn commented Nov 21, 2014

You can verify if a cluster config matches your config by running the undocumented ./ml {env} validate_install. I think it is useful to expose it to public as a validate command. We do need to catch the error, and return a message alike bootstrap. Small change..

@grtjn
Copy link
Contributor Author

grtjn commented Nov 21, 2014

Output would look like this:

$ ./ml local validate
Validating your project installation into MarkLogic on vgtest-v7-ml1...
ERROR: Missing role: test-role (VALIDATION-FAIL):
See MarkLogic Server error log for more details.
... Validation ERROR
$ ./ml local bootstrap
Bootstrapping your project into MarkLogic 7 on vgtest-v7-ml1...
... Bootstrap Complete
$ ./ml local validate
Validating your project installation into MarkLogic on vgtest-v7-ml1...
... Validation SUCCESS

A response with the full list of differences would also be nice, but this would be at least a start..

grtjn added a commit to grtjn/roxy that referenced this issue Jan 20, 2015
paxtonhare added a commit that referenced this issue Jan 20, 2015
@grtjn
Copy link
Contributor Author

grtjn commented Jan 21, 2015

Fixed in dev

@grtjn grtjn closed this as completed Jan 21, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants