We're updating the issue view to help you get more done. 

Integration Environment Documentation - External

Description

External Documentation

  • How do you request a new environment?

  • What information do we need from partners?

    • Name of Org

    • User email

    • Names of the programs they want on test environment

    • Optionally, the external program keys associated with the programs in the test environments

    • Optional? IdP metadata url and slug (uid prefix)

  • And once environment created, what information they would get to get Partners started

    • For instance, there will be a user account created with the user email that the partner provides. They need to click the password reset button from the LMS login page, and we need to note that the reset email may very well end up in their email client's spam folder.

  • How to submit issues to edX if integration environment needs maintenance, bugfix or change.

  • Include this doc with our Partner Integration Guide

Implementation Guide

  • Setup an opsgenie alert ruleset for emails to be sent to Integration_Environment_Support opsgenie email address.

  • Setup a google form to ingest requests from Partners. Forward the result of form submission to the Opsgenie alert email integration.

  • Make sure the google form is secure.

  • Publish the form URL to external document for Partner to reach us.

 

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Status

Assignee

Alex Dusenbery

Reporter

Deen Abdul-Hathi

Labels

Reach

None

Impact

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Category of Work

None

Stakeholders

None

Story Points

1

Sprint

None

Priority

Unset