l3montree-dev / l3montree-dev/devguard
GitLab integration deletion does not remove asset connections
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
When I delete a GitLab integration from the organization settings, the connections of assets that are already linked to this integration are not removed. Deleting the integration should also remove these asset connections.
Steps to reproduce
- Connect an asset to a GitLab integration in the organization settings.
- Delete the GitLab integration.
- Observe that the asset connection to the deleted integration still exists.
I think this is also the same behavior for other integrations, such as GitHub or Jira.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the organization-settings handler for deleting a GitLab integration and the persistence logic for asset connections. Reproduce the three steps described, then verify that deleting the integration removes its existing asset connections; check whether the same behavior applies to GitHub or Jira integrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100