Dryrun mode fails, to 'create' the user based on group membership.
- Dominant language
- Go
- Stars
- 666
- Forks
- 213
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 4
Description
**Describe the bug**
Dryrun doesn't seem to be simulating real behaviour accurately when it comes to 'creating' the user based on group membership.
Where a user needs to be created, to be added to a group. The execution in dry-run mode fails.
**To Reproduce**
Steps to reproduce the behavior:
* Configure DryRun on the lambda
* have a user within scope for a group to be synchronized, but does not exist in IAM Identity Store
**Expected behavior**
The creation of a new user based on group membership, runs successfully.
Contributor guide
Research direction
No file, test, or entry point is named. Reproduce with DryRun enabled, a scoped user absent from AWS IAM Identity Store, and a group synchronization; trace the failure during user creation and verify that the group sync completes successfully without creating the real user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100