redhat-cop / redhat-cop/group-sync-operator
Pruning groups in OKTA is buggy
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 132
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
Randomly we are seeing groups get pruned. I wrote the pruning feature but haven't had a chance yet to look at why it is pruning our groups.
Just wanted to point it out so others know of the issue until I get a chance to debug it
Contributor guide
No contributing guide indexed for this repository
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
The report concerns the existing group-pruning feature and randomly removed OKTA groups, but names no files, tests, or entry points. Start by locating the pruning implementation and reproducing or tracing the unexpected removals; done means identifying and fixing the pruning condition and verifying that intended groups are preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100