fix(datasets): add created_by to ApiToken for get datasets from api correct current user #11450
+66
−6
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.
Summary
This PR Fixes #11331. The problem was that admin-created API keys always showed the owner’s dataset list, even when the owner set “Only Me” permissions.
I added a new field,
created_by
, to theApiToken
model to track who created each API key. This makes sure the correct user and permissions are used when accessing datasets.In the web console, users will now only see the Datasets API keys they created. Old keys without the
created_by
field will still work fine.Screenshots
Checklist
Important
Please review the checklist below before submitting your pull request.
dev/reformat
(backend) andcd web && npx lint-staged
(frontend) to appease the lint gods