feature: Allow installing extra requirements when using the credentials role

[kewne]

This makes the credentials role support the use of edx_django_service_extra_requirements
as done originally in !6400

The end-goal of this is to support theming of the credentials service as described here

Related tickets:

• BB-4342

Testing

1. Launch devstack with credentials service: make dev.up.credentials
2. In the configuration repo, create a docker_inventory.ini file containing just

credentials ansible_connection=docker ansible_host=edx.devstack.credentials

3. Create a playbook credentials_test.yml:

- name: Deploy edX Credentials Service
  hosts: all
  become: True
  gather_facts: True
  vars:
    ENABLE_DATADOG: False
    ENABLE_NEWRELIC: False
    CLUSTER_NAME: 'credentials'
  roles:
    - credentials

4. Run the playbook from the playbooks directory (to ensure ansible.cfg is picked up): ansible-playbook credentials_test.yml -i docker_inventory.ini --skip-tags install:code -e '{ disable_edx_services: true, CREDENTIALS_EXTRA_REQUIREMENTS: [{name: 'lolcat'}], edx_django_service_is_devstack: true}'
5. Assert lolcat is now installed in the credentials virtualenv:

make dev.shell.credentials
source /edx/app/credentials/venvs/credentials/bin/activate
echo test | lolcat 

[openedx-webhooks]

Thanks for the pull request, @kewne! I've created OSPR-5867 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.

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

• supporting documentation
• Open edX discussion forum 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 be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[natabene]

@kewne Thank you for your contribution. Please let me know once it is ready for our review.

[lgp171188]

@kewne, 👍. Before the edX/core committer review, can you edit the description of this PR to mention that this is going to be used to install a theme in the credentials service as documented here?

• I tested this change and verified that it works as expected. It is similar to the changes done in https://github.com/edx/configuration/pull/6400
• I read through the code
• I checked for accessibility issues NA
• Includes documentation NA

[lgp171188]

@natabene, this is now ready for edX/core committer review. The workflows configured for PRs in this repository haven't run for this PR, and there is a message that says First-time contributors need a maintainer to approve running workflows.. So can you approve running the workflows for this PR?

@pomegranited, will you be able to review this PR as a core committer since you reviewed the very similar https://github.com/edx/configuration/pull/6400? Thanks!

[kewne]

@lgp171188

can you edit the description of this PR

Done, thanks!

[pomegranited]

👍 Works perfectly, thank you @kewne !

• I tested this using the beautiful PR test instructions, which made it quick and easy to verify.
• I read through the code
• I checked for accessibility issues N/A
• Includes documentation -- and thanks for updating the PR description with the purpose of this change!
• Commit structure follows OEP-0051 -- close enough 😄
  @kewne Technically, you should have used the prefix feat:, not feature: cf OEP-0051: Conventional Commits#Type.

I'll merge this in 2 days if there are no objections from @edx/devops .

[kewne]

@pomegranited oops! I can amend this to match the expected format, it's not too much trouble.

[pomegranited]

Sure if you want to @kewne :)

[pomegranited]

Approved, see previous comment 👍

[openedx-webhooks]

@kewne 🎉 Your pull request was merged!

Please take a moment to answer a two question survey so we can improve your experience in the future.