Skip to content

feat(drives): add the v1beta1 endpoints for a single drive - #85

Draft
pbleser-oc wants to merge 1 commit into
opencloud-eu:mainfrom
pbleser-oc:feat/drive-v1beta1-aliases
Draft

pbleser-oc wants to merge 1 commit into
opencloud-eu:mainfrom
pbleser-oc:feat/drive-v1beta1-aliases

Conversation

@pbleser-oc

Copy link
Copy Markdown
Member

Adds the v1beta1 operations for a single drive: CreateDriveBeta (POST /v1beta1/drives), and GetDriveBeta, UpdateDriveBeta and DeleteDriveBeta (/v1beta1/drives/{drive-id}).

They take the same requests as their v1.0 counterparts. They return drives in the v1beta1 format, like ListAllDrivesBeta: the permissions use grantedToV2 and the IDs of the unified roles. GetDriveBeta also documents $expand, to get the permissions of the drive's root.

The server side is opencloud-eu/opencloud#3941.

Checked locally, with the generator images of the CI:

  • The spec validates.
  • The generated Go client only gains the four new methods, and opencloud builds and passes the graph tests against it.
  • The TypeScript, PHP and C++/Qt generators run without errors, and the TypeScript client type-checks.

AI assistance: Claude Code (claude-opus-5-5) wrote the spec change and this description.

Clients could only list drives under v1beta1. Getting, creating,
updating and deleting a single drive was only possible under v1.0,
which returns the permissions of a drive with the old role names
instead of the IDs of the unified roles.

Add CreateDriveBeta (POST /v1beta1/drives) and GetDriveBeta,
UpdateDriveBeta and DeleteDriveBeta (/v1beta1/drives/{drive-id}). They
take the same requests as their v1.0 counterparts, and return drives
in the v1beta1 format, like ListAllDrivesBeta. GetDriveBeta also
documents $expand, to get the permissions of the drive's root.

Assisted-by: Claude Code:claude-opus-5-5
@pbleser-oc

Copy link
Copy Markdown
Member Author

Please merge this only once opencloud-eu/opencloud#3941 has reached main: until then, no server has these endpoints, and clients generated from the spec would get 404s. I've switched it to a draft until then.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant