(BB-1009) Applying changes done by #105

[xirdneh]

Configuration Pull Request

Make sure that the following steps are done before merging:

• A DevOps team member has approved the PR if it is code shared across multiple services and you don't own all of the services.
• [ ] Are you adding any new default values that need to be overridden when this change goes live? If so:
  • [ ] Update the appropriate internal repo (be sure to update for all our environments)
  • ~ ] If you are updating a secure value rather than an internal one, file a DEVOPS ticket with details.~
  • [ ] Add an entry to the CHANGELOG.
• [~ ] If you are making a complicated change, have you performed the proper testing specified on the Ops Ansible Testing Checklist? Adding a new variable does not require the full list (although testing on a sandbox is a great idea to ensure it links with your downstream code changes).~
• [ ] Think about how this change will affect Open edX operators. Have you updated the wiki page for the next Open edX release?

[openedx-webhooks]

Thanks for the pull request, @xirdneh! I've created OSPR-3705 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.

Feel free to add as much of the following information to the ticket:

• supporting documentation
• edx-code email threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here.

[openedx-webhooks]

@xirdneh Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future.