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.

Sign up for GitHub

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

Jump to bottom

Database migration for environment_services table in 2.18.0 is too agressive. #3704

Closed
rocketeerbkw opened this issue Apr 4, 2024 · 0 comments · Fixed by #3705
Closed

Database migration for environment_services table in 2.18.0 is too agressive. #3704

rocketeerbkw opened this issue Apr 4, 2024 · 0 comments · Fixed by #3705
Assignees
@bomoko

Comments

@rocketeerbkw
Copy link
Member

Describe the bug

In #3652, the SQL query to delete duplicate services doesn't take into account the environment the services are in. This results in ALL duplicate service names being deleted instead of duplicates per environment. The result is that tasks that require a cli service fail with Environment <id> has no service cli.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bomoko bomoko

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

FIX: fixes migration deletion logic for duplicate environment_services uselagoon/lagoon
2 participants
@rocketeerbkw @bomoko