terraform-provider-gitlab
terraform-provider-gitlab copied to clipboard
gitlabhq
resource/gitlab_label: Add priority attribute
Closes: #69
Blocked by:
- https://github.com/xanzy/go-gitlab/pull/1407
The PR above highlights the issue why this is blocked: basically go-gitlab doesn't support nullable fields in responses, which would be required for the priority field.
This pull request has merge conflicts. Please rebase your branch onto main.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Marking this pull request as stale due to 30 days of inactivity. If this pull request receives no comments in the next 14 days it will be closed. Maintainers can also remove the stale label.
To help this pull request get reviewed, please check that it is rebased onto the latest and is passing automated checks. It also helps if you could reference an issue that the pull request resolves, and create one if it doesn't exist.
@timofurrer - I checked out the graphql API for labels to see if that helped out with this issue... there seems to be an API to create labels, and there is an API to read labels for projects along with an API to read labels for groups however there appears to be no mutation for actually updating a label. So no love here for helping with this issue :-/
Marking this pull request as stale due to 30 days of inactivity. If this pull request receives no comments in the next 14 days it will be closed. Maintainers can also remove the stale label.
To help this pull request get reviewed, please check that it is rebased onto the latest and is passing automated checks. It also helps if you could reference an issue that the pull request resolves, and create one if it doesn't exist.
Hey @timofurrer - I wonder if we could apply the same workaround for go-gitlab here that we did over here: https://github.com/gitlabhq/terraform-provider-gitlab/pull/971#discussion_r835801777
Hey @timofurrer - I wonder if we could apply the same workaround for go-gitlab here that we did over here: #971 (comment)
@PatrickRice-KSC hmmm, where would you see the point to hook into the go-gitlab response handling? I guess what we could do is just query the API ourselves with a custom response struct ...
@timofurrer - Oh shoot, my bad. It's in the response, not the request. I misread the note. Seems like we'd have to make a custom call at this point...
Marking this pull request as stale due to 30 days of inactivity. If this pull request receives no comments in the next 14 days it will be closed. Maintainers can also remove the stale label.
To help this pull request get reviewed, please check that it is rebased onto the latest and is passing automated checks. It also helps if you could reference an issue that the pull request resolves, and create one if it doesn't exist.
Marking this pull request as stale due to 30 days of inactivity. If this pull request receives no comments in the next 14 days it will be closed. Maintainers can also remove the stale label.
To help this pull request get reviewed, please check that it is rebased onto the latest and is passing automated checks. It also helps if you could reference an issue that the pull request resolves, and create one if it doesn't exist.
This PR was closed because it has been stale for 14 days with no activity.