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

Improve delete dataset logic to limit failures causing incorrect quotas #347

Closed
navarroc opened this issue Jan 17, 2025 · 0 comments · Fixed by #348
Closed

Improve delete dataset logic to limit failures causing incorrect quotas #347

navarroc opened this issue Jan 17, 2025 · 0 comments · Fixed by #348
Labels
2storypoint Between 2-6 hours of work, requiring email and/or a brief meeting
Milestone
1.28.0

Comments

@navarroc
Copy link
Member

After deleting the dataset, we should update the users quota before removing the layer from the geoserver. A failure (e.g. network issue) could cause the dataset to be deleted, but the quota remain because of the exception.
@navarroc navarroc added the 2storypoint Between 2-6 hours of work, requiring email and/or a brief meeting label Jan 17, 2025
navarroc added a commit that referenced this issue Jan 17, 2025
@navarroc
Fixes #347 - changed order of delete dataset operations
c81f5e8
@navarroc navarroc linked a pull request Jan 17, 2025 that will close this issue
Fixes #347 - changed order of delete dataset operations #348
Merged
@navarroc navarroc added this to the 1.28.0 milestone Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
2storypoint Between 2-6 hours of work, requiring email and/or a brief meeting
Projects
None yet
Milestone
1.28.0
Development

Successfully merging a pull request may close this issue.

Fixes #347 - changed order of delete dataset operations IN-CORE/incore-services
1 participant
@navarroc