-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change mount_series
endpoint to accept and move existing series
#1225
Conversation
a123e17
to
6a2d43e
Compare
fe39123
to
a9556b3
Compare
a9556b3
to
156f1ab
Compare
156f1ab
to
dfc0d4d
Compare
6a2d43e
to
fb675ac
Compare
0f37033
to
fb675ac
Compare
6fa85fe
to
bc1902d
Compare
fb675ac
to
3a5d83a
Compare
This comment was marked as resolved.
This comment was marked as resolved.
3a5d83a
to
a06ba4e
Compare
a06ba4e
to
5be04f0
Compare
This comment has been minimized.
This comment has been minimized.
5be04f0
to
adc795b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We just discussed this in chat, I'm just writing it down here for protocol.
I was still not too happy with very overloaded move
API. So the idea now to wait for #1179 and then add three more API endpoints to end up with these:
createRealmLineage(realms: { name: string, pathSegment: string })
prefigureSeries(series: NewSeries)
(not necessarily final name)addSeriesMountPoint(series_oc_id: string, realm_path: string)
removeSeriesMountPoint(realm_path: string)
(maybe also pass series id to check stuff?)
The admin UI is then changed to send a GraphQL request with multiple mutations in them. GraphQL guarantees us, that these are executed in order. And Tobira uses one DB transaction per GraphQL request, so the whole operation is atomic. Nice!
We do need to keep the old mountSeries
endpoint around for some while, until the last admin UI using it is not supported anymore, but that's not a big problem.
Note though that the individual endpoints (especially the MountPoint
ones) are still... no atomic perfectly defined operation. It still represents a "high level task" (like the current mountSeries
) instead of manipulating Tobira's DB objects directly.
This comment was marked as resolved.
This comment was marked as resolved.
adc795b
to
3f63c30
Compare
3f63c30
to
4f86349
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I sadly found a few things that need fixing. But I think they should all be straight forward? The general direction is good.
df91940
to
ac46ed4
Compare
4f86349
to
6529c59
Compare
This comment has been minimized.
This comment has been minimized.
6529c59
to
bee6021
Compare
This comment has been minimized.
This comment has been minimized.
bee6021
to
482c721
Compare
482c721
to
bd9b1b3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good changes, I only have a few small remarks that should be easy to fix!
Oh and: once the admin UI PRs are merged, we should adjust our github action script ( |
bd9b1b3
to
274a1f0
Compare
This is necessary for an upcoming admin UI feature which will allow admins to change the path of series pages with no other blocks.
274a1f0
to
1bf3720
Compare
This adds - a) an endpoint to get paths of pages in Tobira that host an event - b) an endpoint to update the path of a series in Tobira This shouldn't break any existing behaviour. These are needed for additional requirements of opencast/opencast-admin-interface#311. Corresponding Tobira and admin-UI PRs: elan-ev/tobira#1225, opencast/opencast-admin-interface#878. ### Your pull request should… * [ ] have a concise title * [ ] [close an accompanying issue](https://docs.opencast.org/develop/developer/#participate/development-process/#automatically-closing-issues-when-a-pr-is-merged) if one exists * [ ] [be against the correct branch](https://docs.opencast.org/develop/developer/development-process#acceptance-criteria-for-patches-in-different-versions) * [ ] include migration scripts and documentation, if appropriate * [ ] pass automated tests * [ ] have a clean commit history * [ ] [have proper commit messages (title and body) for all commits](https://medium.com/@steveamaza/e028865e5791)
This is necessary for an upcoming admin UI feature which will allow admins to change the path of series pages with no other blocks (part of opencast/opencast-admin-interface#311).
This shouldn't break any existing behaviour.
Related Opencast and admin UI PRs: opencast/opencast#6091, opencast/opencast-admin-interface#878.