feat: TNL-11173 Authoring API is v0 for now #33644
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bszabo
force-pushed
the
bszabo/TNL-11173-authoring-api-at-v0
branch
from
51a4abb to
2d0c205
Compare
jesperhodge
approved these changes
Nov 3, 2023
|
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
|
2U Release Notice: This PR has been deployed to the edX production environment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This ticket contains work from the TNL-11173 JIRA task.
The changes made here move existing authoring API capabilities from their former v1-based routes to v0-routes. This is to emphasize that the current API is experimental and expected to be deprecated in short order. It's also consistent with othern TNL work exposing public APIs under v0-based 'authoring' routes on our AWS API Gateway.
Supporting information
Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.
Be sure to check they are publicly readable, or if not, repeat the information here.
Testing instructions
Use the same testing procedures that applied when the studio API routes were initially created. The only change that applies is that the routes are now v0 routes instead of v1 routes. Continuing to make requests off of the v1 routes should result in 404 (not found) errors.
Deadline
This PR is essential for carrying out the end-to-end tests we need to verify that our API Gateway configuration is actually working. It is therefore time sensitive.
Other information