Add REST endpoints for bulk tagging & un-tagging of projects #3894
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.
Description
Adds REST endpoints for bulk tagging & un-tagging of projects.
Addressed Issue
Relates to #586
Additional Details
Bulk operations are currently limited to 100 projects per request. We can raise this limit if users need it. But for a beginning it's better to stay conservative since limiting it later would mean a breaking change.
Both
POST
andDELETE
endpoints are implemented to be atomic operations.Portfolio ACLs are considered:
There will be no
HTTP 403
response if tagging or un-tagging of inaccessible projects is attempted.Checklist
This PR fixes a defect, and I have provided tests to verify that the fix is effectiveThis PR introduces changes to the database model, and I have added corresponding update logicThis PR introduces new or alters existing behavior, and I have updated the documentation accordingly