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

[Task]: Move updateSuperUser migration from repetitive migration strategy to bean creation strategy #33624

Closed
vivonk opened this issue May 21, 2024 · 1 comment
Assignees
Labels
Task A simple Todo

Comments

@vivonk
Copy link
Contributor

vivonk commented May 21, 2024

SubTasks

  • Create beans for updateUserUser
  • Coomunicate the same decision with the wider audience to adhere with this practice so that we dont' have to replicate these repeating migrations separately for MongoDB and Postgres. Rather single code works for both
@vivonk vivonk added Task A simple Todo Billing & Licensing Product Issues pertaining to licensing, billing and usage across self serve and enterprise customers labels May 21, 2024
@vivonk vivonk self-assigned this May 21, 2024
@github-actions github-actions bot removed the Billing & Licensing Product Issues pertaining to licensing, billing and usage across self serve and enterprise customers label May 21, 2024
@vivonk
Copy link
Contributor Author

vivonk commented Jun 14, 2024

As discussed, we are not much interested in moving repeating migrations as bean on release branch as it doesn't help much with code changes efforts required going forward so we are not going a head with this appraoch.

@vivonk vivonk closed this as completed Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task A simple Todo
Projects
None yet
Development

No branches or pull requests

1 participant