Send email at Duo seat bulk assignment for SM

Roy Liurequested to merge
488583-add-worker-for-bulk-send-duo-seat-assignment-email into master

What does this MR do and why?

For self-managed instances, add a worker to send email notifying users that were granted duo seats during a bulk assignment. Currently, we have both emails for Duo Pro and Duo Enterprise to send.

References

Please include cross links to any resources that are relevant to this MR This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

  • Related to #488583

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

No UI changes.

How to set up and validate locally

If you already have an EE self-managed instance with Duo Pro, you can skip to step 6

  1. Set up your GDK to point to CustomersDot Staging. In gdk.yml:
license:
 customer_portal_url: https://customers.staging.gitlab.com
 license_mode: test
  1. Also make sure you have GITLAB_SIMULATE_SAAS env variable as a falsy value, then you can reconfigure and restart GDK.
  2. Purchase a license with a Duo add-on (can be Duo Enterprise or Duo Pro) on https://customers.staging.gitlab.com
    • Follow this URL to purchase an Ultimate self-managed license (see these docs for details)
    • Once you have purchased the self-managed license, purchase a Duo add-on following these steps
    • You can use a test credit card to complete these purchases
  3. Copy the activation code for the license from CustomersDot
  4. Go to the Admin area > Subscription and upload the activation code
  5. Once uploaded, go to Admin area > GitLab Duo tab to view the GitLab Duo seats page (you might need to hit the sync icon in Subscription for GitLab Duo purchase to show up)
  6. Once you have the seats toggle show up, assign multiple users seats by clicking the checkbox on the left side of username
  7. Go to /rails/letter_opener, you should see the emails: for reference, sample email: !164104 (merged).
Edited by Roy Liu

Merge request reports