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

Add a task to perform index comparison i.e. configuration file with current DB configuration prior deployment #374

Closed
pankajsahu-11 opened this issue Aug 31, 2018 · 2 comments

Comments

@pankajsahu-11
Copy link

Hi Team,
We are part of preferred MarkLogic client/partner team and need a new ml-gradle task with following functionality which would be helpful while multiple projects are using same configuration file and migrate from DEV to QA/PRD environments:

  • perform comparison of indexes from configuration file with indexes present in DB
  • list down the indexes which would be added/removed as part of this deployment
  • prompt for confirmation i.e. Yes/No prior proceeding with mlDeploy or configuration deployment

Regards...Pankaj Sahu

@rjrudin
Copy link
Contributor

rjrudin commented Aug 31, 2018

How soon are you needing this? Note that this is largely an exercise in comparing JSON documents, which could be done in custom Java or Groovy code in your build.gradle file. Have you tried doing that yet? https://github.com/marklogic-community/ml-gradle/wiki/Writing-your-own-task provides some guidance on writing a custom task that talks to the Manage API.

@rjrudin
Copy link
Contributor

rjrudin commented Dec 29, 2018

#415 adds "mlPreviewDeploy". It will show all changes as part of a deployment, not just index changes for a database. There's no confirmation with proceeding - that would just be a matter of running mlDeploy after confirming that the preview looks sufficient.

I'm closing this because of #415 - try that out (will be in 3.11.0 which should be released in the next week or so), and if you feel strongly about a confirmation process, please write up a new ticket and describe how it would work and improve upon running mlPreviewDeploy and then mlDeploy.

@rjrudin rjrudin closed this as completed Dec 29, 2018
rjrudin added a commit that referenced this issue Aug 23, 2024
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

No branches or pull requests

2 participants