Dont use sudo while creating milestones. #30
Conversation
This file contains hidden or 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
During migration of some bugzilla tickets i noticed random 403 forbidden errors during milestone creation. Just as during issue creation, the sudo flag is set for creating a milestone too, means it attempts to create the milestone with the user the current ticket is processed (and which was missing some access rights in my case). As we are using an administrative account for migration anyways its not requird to set sudo value in the headers and i think it is perfectly fine to use the project's administrative account to create them.
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.
During migration of some bugzilla tickets i noticed random 403
forbidden errors during milestone creation. Just as during issue
creation, the sudo flag is set for creating a milestone too, means it
attempts to create the milestone with the user the current ticket is
processed (and which was missing some access rights in my case).
As we are using an administrative account for migration anyways its not
requird to set sudo value in the headers and i think it is perfectly
fine to use the project's administrative account to create them.