BFF Utility for Organization Management #937
Conversation
Codecov ReportBase: 43.99% // Head: 43.93% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #937 +/- ##
==========================================
- Coverage 43.99% 43.93% -0.07%
==========================================
Files 688 688
Lines 25573 25609 +36
Branches 1562 1565 +3
==========================================
- Hits 11252 11251 -1
- Misses 12874 12911 +37
Partials 1447 1447
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
bbengfort
force-pushed
the
sc-11778/bffutil
branch
from
a90bb1c to
e292a30
Compare
| if err = db.UpdateOrganization(curOrg); err != nil { | ||
| return cli.Exit(fmt.Errorf("could not update user's current organization: %w", err), 1) | ||
| } | ||
| } |
There was a problem hiding this comment.
Do we need to make sure the user does not maintain their role if they are a leader in their "default" organization and they are moved to an organization where they shouldn't be a leader?
There was a problem hiding this comment.
Managing roles is a little annoying -- in the first pass at this, the manual trigger will be used for users that have the TSP role, so changing the role isn't too important, and if it is we can do it in auth0. I'm hopeful that the collaborators management feature will come online before we have to really use bffutil in earnest -- but we could create a future story for roles if we think we need it.
There was a problem hiding this comment.
Sounds good to me, just wanted to make sure we thought of that; since we are primarily using this for TSPs I'm 100% okay with not attempting to change roles.
Scope of changes
Adds a
bffutilCLI program that will help us manually manage organizations in order to get CipherTrace TSP users access to old/previous organizations and for us to manage all organizations in the BFF.TODO:
Fixes SC-11778
Type of change
Acceptance criteria
leveldbstore namespace issue?bffutilcommand to the bff Dockerfile?bffutilon the pod?Author checklist
Reviewer(s) checklist
bffutildeployment