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

ref(deletion) Consolidate group deletion and improve logging #28475

Merged
merged 1 commit into from
Sep 16, 2021

Conversation

markstory
Copy link
Member

We had two different implementations of group deletion. This change consolidates those into a single path and fixes split group hashes being removed by list page delete operations.

I've also added the organization_id to group deletion messages. This helps improve log queries like 'did acme org delete any issues recently' which comes up when customers notice discrepancies between the events they currently have and the usage we've tracked.

We had two different implementations of group deletion. This change
consolidates those into a single path and fixes split group hashes being
removed by list page delete operations.

I've also added the organization_id to group deletion messages. This
helps improve log queries like 'did acme org delete any issues recently'
which comes up when customers notice discrepancies between the events
they currently have and the usage we've tracked.
@markstory markstory requested review from untitaker and a team September 9, 2021 21:20
@markstory markstory merged commit 5f4f114 into master Sep 16, 2021
@markstory markstory deleted the ref-group-delete-consolidate branch September 16, 2021 20:16
matejminar pushed a commit that referenced this pull request Sep 17, 2021
We had two different implementations of group deletion. This change
consolidates those into a single path and fixes split group hashes being
removed by list page delete operations.

I've also added the organization_id to group deletion messages. This
helps improve log queries like 'did acme org delete any issues recently'
which comes up when customers notice discrepancies between the events
they currently have and the usage we've tracked.
@github-actions github-actions bot locked and limited conversation to collaborators Oct 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants