Skip to content

Conversation

@danpoletaev
Copy link
Contributor

@danpoletaev danpoletaev commented Dec 5, 2025

We noticed that we don't have information about updating generalAccess in docs.

This PR updates docs to include generalAccess for update(PUT) endpoints of:

  • KV stores
  • RQ
  • Datasets
  • Runs

Note

Documents and exposes generalAccess in schemas and PUT endpoints for runs, datasets, key‑value stores, and request queues, and expands the run update endpoint to cover both status and access.

  • OpenAPI Schemas:
    • actor-runs/Run.yaml: Add generalAccess (enum) and include it in required.
    • Add generalAccess (enum) to datasets/Dataset.yaml, key-value-stores/KeyValueStore.yaml, request-queues/RequestQueue.yaml.
    • Update request schemas to accept generalAccess (with examples): datasets/UpdateDatasetRequest.yaml, request-queues/UpdateRequestQueueRequest.yaml, store/UpdateStoreRequest.yaml, actor-runs/UpdateRunRequest.yaml.
  • PUT Endpoints:
    • datasets@{datasetId}.yaml, key-value-stores@{storeId}.yaml, request-queues@{queueId}.yaml: Update descriptions to allow updating name and generalAccess; add generalAccess to request examples.
    • actor-runs@{runId}.yaml: Rename summary to "Update run" and expand description to cover statusMessage and generalAccess (allowed values, effects).

Written by Cursor Bugbot for commit abbd7d2. Configure here.

@danpoletaev danpoletaev requested review from TC-MO and stepskop December 5, 2025 10:49
@danpoletaev danpoletaev self-assigned this Dec 5, 2025
@danpoletaev danpoletaev added the adhoc Ad-hoc unplanned task added during the sprint. label Dec 5, 2025
@danpoletaev danpoletaev removed the request for review from fnesveda December 5, 2025 10:50
@github-actions github-actions bot added the t-core-services Issues with this label are in the ownership of the core services team. label Dec 5, 2025
@danpoletaev danpoletaev removed the request for review from janbuchar December 5, 2025 10:50
Comment on lines 70 to 76
generalAccess:
type: string
enum:
- RESTRICTED
- ANYONE_WITH_ID_CAN_READ
- FOLLOW_USER_SETTING
example: RESTRICTED
Copy link
Contributor

Choose a reason for hiding this comment

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

I believe that this enum could be extracted into the components and referenced here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point, refactored 👍

@apify-service-account
Copy link

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

@TC-MO TC-MO requested a review from marcel-rbro December 9, 2025 14:33
Copy link
Contributor

@stepskop stepskop left a comment

Choose a reason for hiding this comment

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

Agree with Honza here. Besides that, good 👍

@apify-service-account
Copy link

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

@apify-service-account
Copy link

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

summary: Update status message
summary: Update run
description: |
This endpoint can be used both to update the run’s status message and to configure its general resource access level.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
This endpoint can be used both to update the run’s status message and to configure its general resource access level.
This endpoint can be used to update both the run’s status message and to configure its general resource access level.

Allowed values:
* `FOLLOW_USER_SETTING` - The run inherits the general access setting from the account-level.
Copy link
Contributor

Choose a reason for hiding this comment

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

Either "account level" or "account-level permissions/settings/whatever".

* `FOLLOW_USER_SETTING` - The run inherits the general access setting from the account-level.
* `ANYONE_WITH_ID_CAN_READ` - The run can be viewed anonymously by anyone who has its ID.
* `RESTRICTED` - Only users with explicit access to the resources can access the run.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* `RESTRICTED` - Only users with explicit access to the resources can access the run.
* `RESTRICTED` - Only users with explicit access to the resource can access the run.

- ANYONE_WITH_ID_CAN_READ
- FOLLOW_USER_SETTING
example: RESTRICTED
description: "Defines general access level for the resource."
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
description: "Defines general access level for the resource."
description: Defines the general access level for the resource.

Comment on lines 49 to 55
generalAccess:
type: string
enum:
- RESTRICTED
- ANYONE_WITH_ID_CAN_READ
- FOLLOW_USER_SETTING
example: RESTRICTED
Copy link
Contributor

Choose a reason for hiding this comment

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

Is the duplicate content necessary? Can't a reference be used here, as in the KeyValueStore.yaml file?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point, missed that 👍

@apify-service-account
Copy link

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

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

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-core-services Issues with this label are in the ownership of the core services team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants