feat: enterprise sso orchestrator api client implementation

[alex-sheehan-edx]

https://2u-internal.atlassian.net/browse/ENT-7571

Merge checklist:

• Any new requirements are in the right place (do not manually modify the requirements/*.txt files)
  • base.in if needed in production but edx-platform doesn't install it
  • test-master.in if edx-platform pins it, with a matching version
  • make upgrade && make requirements have been run to regenerate requirements
• make static has been run to update webpack bundling if any static content was updated
• ./manage.py makemigrations has been run
  • Checkout the Database Migration Confluence page for helpful tips on creating migrations.
  • Note: This must be run if you modified any models.
    • It may or may not make a migration depending on exactly what you modified, but it should still be run.
  • This should be run from either a venv with all the lms/edx-enterprise requirements installed or if you checked out edx-enterprise into the src directory used by lms, you can run this command through an lms shell.
    • It would be ./manage.py lms makemigrations in the shell.
• Version bumped
• Changelog record added
• Translations updated (see docs/internationalization.rst but also this isn't blocking for merge atm)

Post merge:

• Tag pushed and a new version released
  • Note: Assets will be added automatically. You just need to provide a tag (should match your version number) and title and description.
• After versioned build finishes in GitHub Actions, verify version has been pushed to PyPI
  • Each step in the release build has a condition flag that checks if the rest of the steps are done and if so will deploy to PyPi.
    (so basically once your build finishes, after maybe a minute you should see the new version in PyPi automatically (on refresh))
• PR created in edx-platform to upgrade dependencies (including edx-enterprise)
  • This must be done after the version is visible in PyPi as make upgrade in edx-platform will look for the latest version in PyPi.
  • Note: the edx-enterprise constraint in edx-platform must also be bumped to the latest version in PyPi.

[johnnagro]

is this the correct way to call get_configuration_value? it doesn't seem correct to me to supply the setting as the default value for when the setting does not exist? perhaps i misunderstand

[alex-sheehan-edx]

it's how we've done it in other areas

[alex-sheehan-edx]

edx-enterprise/enterprise/models.py

Lines 625 to 661 in 426413c

	get_configuration_value('LMS_ROOT_URL', settings.LMS_ROOT_URL),
	reverse(
	'enterprise_course_enrollment_page',
	kwargs={'enterprise_uuid': self.uuid, 'course_key': course_key}
	)
	)
	return utils.update_query_parameters(url, utils.get_enterprise_utm_context(self))
	def get_course_run_enrollment_url(self, course_run_key):
	"""
	Return enterprise landing page url for the given course.
	Arguments:
	course_run_key (str): The course run id for the course to be displayed.
	Returns:
	(str): Enterprise landing page url.
	"""
	url = urljoin(
	get_configuration_value('LMS_ROOT_URL', settings.LMS_ROOT_URL),
	reverse(
	'enterprise_course_run_enrollment_page',
	kwargs={'enterprise_uuid': self.uuid, 'course_id': course_run_key}
	)
	)
	return utils.update_query_parameters(url, utils.get_enterprise_utm_context(self))
	def get_program_enrollment_url(self, program_uuid):
	"""
	Return enterprise landing page url for the given program.
	Arguments:
	program_uuid (str): The program UUID.
	Returns:
	(str): Enterprise program landing page url.
	"""
	url = urljoin(
	get_configuration_value('LMS_ROOT_URL', settings.LMS_ROOT_URL),

[johnnagro]

we may still want to extend from something inside edx-rest-api-client (perhaps a version which supports BasicAuth rather than OAuth) so that we benefit from all the nice default addons like custom user-agents which are app aware, request id forwarding, etc.

[alex-sheehan-edx]

I didn't see anything about basic auth in the rest api client but I can double check