Skip to content

chore(api): add the new 'ownership' parameter for listing storages#2208

Merged
nmanerikar merged 3 commits intomasterfrom
chore/storages-ownership
Jan 29, 2026
Merged

chore(api): add the new 'ownership' parameter for listing storages#2208
nmanerikar merged 3 commits intomasterfrom
chore/storages-ownership

Conversation

@nmanerikar
Copy link
Copy Markdown
Contributor

@nmanerikar nmanerikar commented Jan 28, 2026

Document the new 'ownership' parameter in the listing requests for storages.


Note

Documents a new optional ownership query parameter for storage listing endpoints to filter by resource ownership.

  • Adds ownership to GET listings for datasets, key-value stores, and request queues (datasets.yaml, key-value-stores.yaml, request-queues.yaml)
  • Accepts ownedByMe or sharedWithMe; default remains all accessible resources

Written by Cursor Bugbot for commit ee02f2e. Configure here.

@nmanerikar nmanerikar requested review from raethlo and tobice January 28, 2026 16:43
@nmanerikar nmanerikar self-assigned this Jan 28, 2026
@nmanerikar nmanerikar added the t-core-services Issues with this label are in the ownership of the core services team. label Jan 28, 2026
@apify-service-account
Copy link
Copy Markdown

Preview for this PR was built for commit ee02f2e7 and is ready at https://pr-2208.preview.docs.apify.com!

Comment thread apify-api/openapi/paths/datasets/datasets.yaml Outdated
Comment thread apify-api/openapi/paths/datasets/datasets.yaml Outdated
@apify-service-account
Copy link
Copy Markdown

Preview for this PR was built for commit 462f9f87 and is ready at https://pr-2208.preview.docs.apify.com!

Copy link
Copy Markdown
Contributor

@tobice tobice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Btw that's a lot of reviewers 😄 I'd say one person from the tooling team and one person from us should be enough.

Not sure why Franta is there, marked as an owner 🤔

@nmanerikar nmanerikar requested review from janbuchar and removed request for fnesveda and raethlo January 29, 2026 09:14
@janbuchar
Copy link
Copy Markdown
Contributor

Btw that's a lot of reviewers 😄 I'd say one person from the tooling team and one person from us should be enough.

Not sure why Franta is there, marked as an owner 🤔

The original idea was that I'm there to check that the OpenAPI spec follows best practices and Franta is supposed to review the correctness of what's being written there. We can re-evaluate this for sure.

Comment on lines +1 to +5
type: string
enum:
- ownedByMe
- sharedWithMe
examples: [ownedByMe]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In OpenAPI 3.1 (which we now use), it should be possible to write enums like this:

type: string
oneOf:
  - const: ownedByMe
    description: Return only storages owned by the user.
  - const: sharedWithMe
    description: Return only storages shared with the user by other users.

The benefit of this is that you don't have to repeat the documentation three times. Can you please try it?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did try it like that before. But that means that we end up with the generic term "storages" instead of the specific terms ("datasets", et.c.). I think using the generic term might be confusing for the user - from their POV they are looking at 'datasets' documentation, and suddenly the docs refer to 'storages'... are they the same? different?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's also a valid point. Resolve it as you see fit 🙂

@nmanerikar nmanerikar merged commit b4c35ab into master Jan 29, 2026
15 of 16 checks passed
@nmanerikar nmanerikar deleted the chore/storages-ownership branch January 29, 2026 19:57
@raethlo raethlo added the validated Issues that are resolved and their solutions fulfill the acceptance criteria. label Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-core-services Issues with this label are in the ownership of the core services team. validated Issues that are resolved and their solutions fulfill the acceptance criteria.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants