Skip to content

Conversation

timofurrer
Copy link
Member

@timofurrer timofurrer commented Mar 26, 2022

We should be able to merge this :)

@timofurrer timofurrer added the blocked We are currently blocked to implement this label Mar 26, 2022
@timofurrer timofurrer added this to the v3.X (first release for GitLab 14.10) milestone Mar 26, 2022
@timofurrer timofurrer requested a review from armsnyder March 26, 2022 17:16
@timofurrer timofurrer self-assigned this Mar 26, 2022
@github-actions github-actions bot added provider resource Adds or modifies a resource size/M labels Mar 26, 2022
@Shocktrooper
Copy link
Collaborator

@timofurrer Is there any GitHub action we can use that is similar to the !RemindMe 1 week/1 month/etc. of reddit. Where there can be a post/notification to look at a PR/issue when a certain period of time is reached? This would be useful for when functionality in the provider is blocked by a functionality that is scheduled to be released in a future GitLab version so as not to forget about something like this PR

@timofurrer
Copy link
Member Author

@Shocktrooper a quick search revealed at least one: https://github.com/agrc/reminder-action

Though I'm not really sure if it's worth the maintenance - GitLab releases are always at the same day of the month, every month, thus it's kinda hard to miss - and I've created a milestone where to assign these issues / PRs. I think that gives us an additional benefit over the reminder, because we can actually filter them :)

@Shocktrooper
Copy link
Collaborator

@timofurrer The milestones seem like a good way to go. I was just thinking for some issues where maybe the functionality is scheduled a long way down the line/not at all vs within a few months. They would be reminders to check if the upstream API has been released such as for an issue like this where GitLab has not added the functionality at the time and we might want to check in say like 6 months

@timofurrer timofurrer marked this pull request as draft March 28, 2022 15:24
@timofurrer
Copy link
Member Author

This would break compatibility to GitLab < 14.10

@github-actions github-actions bot added the merge-conflict PR cannot be merged due to a merge conflict label Mar 31, 2022
@github-actions
Copy link

This pull request has merge conflicts. Please rebase your branch onto main.

@timofurrer timofurrer removed this from the v3.X (first release for GitLab 14.10) milestone Apr 22, 2022
@github-actions
Copy link

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.

@github-actions
Copy link

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.

@github-actions
Copy link

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.

@Shocktrooper
Copy link
Collaborator

@timofurrer Is this unblocked now that 14.10 has been released and the prerequisite PR has been merged?

@timofurrer timofurrer force-pushed the feature/get-pat-gat branch from a371c22 to c253023 Compare July 26, 2022 12:55
@github-actions github-actions bot removed the merge-conflict PR cannot be merged due to a merge conflict label Jul 26, 2022
@github-actions
Copy link

Conflicts are resolved. Thank you! 😀

@timofurrer timofurrer removed the blocked We are currently blocked to implement this label Jul 26, 2022
@timofurrer timofurrer marked this pull request as ready for review July 26, 2022 12:55
@timofurrer timofurrer added this to the v3.17.0 milestone Jul 26, 2022
Copy link
Collaborator

@RicePatrick RicePatrick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Losing internet on the flight since I'm landing, but one comment so far 😄

@timofurrer timofurrer force-pushed the feature/get-pat-gat branch from c253023 to 50a1d06 Compare July 28, 2022 08:30
@timofurrer timofurrer requested a review from RicePatrick July 28, 2022 08:31
@RicePatrick
Copy link
Collaborator

No other comments from reviews, thanks @timofurrer and @Shocktrooper !

@RicePatrick RicePatrick merged commit 6be9174 into gitlabhq:main Jul 29, 2022
@github-actions
Copy link

This functionality has been released in v3.17.0 of the Terraform GitLab Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue. Thank you!

@github-actions github-actions bot locked and limited conversation to collaborators Nov 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

provider resource Adds or modifies a resource size/M

Development

Successfully merging this pull request may close these issues.

3 participants