Fixes #90 - added a script to update service object ownership #91
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…wned by incore if the object is in the public incore space
Rashmil-1999
approved these changes
Mar 27, 2025
No, we shouldn't need a cron job. I think at some point we need to fix the spaces endpoint so if an admin adds a dataset to the "incore" space, then the owner field gets updated to be "incore". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This script will update the owner of any dataset, hazard or DFR3 object that is in the public "incore" space to be owned by "incore". The original author will still be the creator, but the ownership will transfer to incore to prevent accidental deletion of public data.