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

Ability to disable database evolutions on a datasource basis #1383

Closed
holajsh opened this issue Feb 15, 2022 · 0 comments · Fixed by #1384
Closed

Ability to disable database evolutions on a datasource basis #1383

holajsh opened this issue Feb 15, 2022 · 0 comments · Fixed by #1384
Labels
Milestone

Comments

@holajsh
Copy link
Contributor

holajsh commented Feb 15, 2022

It would be really convenient to be able to disable database evolutions on a datasource basis.
The configuration currently support a global evolutions.enabled=false parameter.
Such a parameter could be present per datasource: db.datasourcename.evolutions.enabled=false

holajsh added a commit to holajsh/play1 that referenced this issue Feb 15, 2022
holajsh added a commit to holajsh/play1 that referenced this issue Feb 15, 2022
xael-fry added a commit that referenced this issue Feb 21, 2022
…datasource

[#1383] 🆕 Ability to disable database evolutions on a datasource basis
@xael-fry xael-fry added this to the 1.7.0 milestone Feb 21, 2022
holajsh added a commit to holajsh/play1 that referenced this issue Mar 25, 2022
xael-fry added a commit that referenced this issue Apr 2, 2022
…datasource

[#1383] ♻ Support disabled evolutions for command line operations
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants