Page Comparison

...

• Status
  colour Green title In FC-18

  https://github.com/openedx/edx-drf-extensions/issues/333

  • New implementation ticket for https://github.com/openedx/public-engineering/issues/83

  • This would simplify authentication and maintenance, but wouldn’t necessarily add functionality.

• Status
  colour Green title In FC-18

  https://github.com/openedx/edx-drf-extensions/issues/327

• https://github.com/openedx/public-engineering/issues/189

  • Related: For some of the past removal work, the new api client wasn’t used, and instead a straight requests object was used and worked with the user’s JWT for service-to-service calls.

    • The intention was not to add this functionality to the new client, because it was thought that the client credentials token should be used instead.

    • If feels like we should have an ADR that clarifies what should be used where, and potentially enhances the client if we wish to allow for other ways of using it.

    • The client also provided shared observability, but that only works when it is used.

• https://github.com/openedx/edx-drf-extensions/issues/284

  • To be considered.

• https://github.com/openedx/public-engineering/issues/190

• https://github.com/openedx/public-engineering/issues/82

• Jira Legacy
  server System JIRA serverId 13fd1930-5608-3aac-a5dd-21b934d3a4b4 key ARCHBOM-1172

  (“unfinished”)

• A DEPR should be created for this.

Probably requires working in Prospectus

https://github.com/openedx/edx-platform/issues/32343

• Requires working in Prospectus, edx.org’s private marketing site, so this is not a good candidate for community work.

• Jira Legacy
  server System JIRA serverId 13fd1930-5608-3aac-a5dd-21b934d3a4b4 key ARCHBOM-1077

  (“unfinished”)

  • Related?

    Jira Legacy
    server System JIRA serverId 13fd1930-5608-3aac-a5dd-21b934d3a4b4 key ARCHBOM-1168

    (“unfinished”)

...