-
Notifications
You must be signed in to change notification settings - Fork 3
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
1337 email owner as system admin group (un)assigned #3253
base: develop
Are you sure you want to change the base?
Conversation
…aft-tech/TANF-app into 1337-sys-admin-permission-change-email
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #3253 +/- ##
===========================================
- Coverage 91.52% 91.52% -0.01%
===========================================
Files 297 298 +1
Lines 8415 8456 +41
Branches 608 612 +4
===========================================
+ Hits 7702 7739 +37
- Misses 603 606 +3
- Partials 110 111 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
from tdpservice.users.models import User | ||
from tdpservice.email.email_enums import EmailType | ||
from tdpservice.email.email import automated_email, log | ||
from tdpservice.email.tasks import get_system_owner_email |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there a reason for the imports in the function? i see it in other functions in this file, so just curious
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think originally I got circular error, but will check back again because I changed things around
ACTIONS = { | ||
'PRE_REMOVE': 'pre_remove', | ||
'PRE_ADD': 'pre_add', | ||
'PRE_CLEAR': 'pre_clear' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
enum?
<!-- Body copy --> | ||
<p style="color: #000000;"> | ||
|
||
<p>The following Admin User account for the TANF Data Portal (TDP) has been {{ action }}.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This reads a little bit weird with "added" and "removed" as the action
. Could we do "assigned" and "unassigned"? Or change the sentence a little.
"The System Admin role has been (assigned/unassigned) for a user of the TANF Data Portal (TDP)"
just a suggestion. sounds a little like the account has been deleted otherwise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor feedback. works as written
@raftmsohani one note i forgot to make: the description says "system admins" should receive the email, but i believe it should say "system owners" also, the addition of the new System Owners group means that the frontend no longer shows the expected links (kibana, grafana, admin) |
@jtimpe I don't see anything wrong, basically when system admin group is being (un)assigned then system owner should receive email |
@raftmsohani is it expected for sys admins to create this new user group? if so, why? Additionally, what permissions does this user group need? |
Instead of creating the group in migrations, we decided to create it one manually in prod, and then pull all group creations out of migrations and add it to load data command. I thought the new SystemOwner group is what the ticket is asking. I assume same permissions as OFAAdmin?? |
okay; is this approach simpler? if so, can you attach a video demonstrating how to do this? @raftmsohani |
Summary of Changes
Provide a brief summary of changes
Pull request closes #1337 _
How to Test
The following screenshot shows an example of email template for assignment:
Deliverables
More details on how deliverables herein are assessed included here.
Deliverable 1: Accepted Features
Checklist of ACs:
lfrohlich
and/oradpennington
confirmed that ACs are met.Deliverable 2: Tested Code
CodeCov Report
comment in PR)CodeCov Report
comment in PR)Deliverable 3: Properly Styled Code
Deliverable 4: Accessible
iamjolly
andttran-hub
using Accessibility Insights reveal any errors introduced in this PR?Deliverable 5: Deployed
Deliverable 6: Documented
Deliverable 7: Secure
Deliverable 8: User Research
Research product(s) clearly articulate(s):