-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Third times a charm for protected environments #938
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome @Shocktrooper 👋
It looks like this is your first submission to the Terraform GitLab Provider! If you haven’t already done so, please make sure you have checked out our CONTRIBUTING.md guide to make sure your contribution has all the necessary elements in place for a successful approval.
Thanks again, and welcome to the community! 😃
@timofurrer here is the new PR on my fork. I left a comment in one of the files and not sure I put the right value. Other than that I am not sure if I modified the other files correctly to conform to the changes the provider went through |
@timofurrer I have some unit tests failing and not sure why. If you have some free time to sync up I would like to try and figure out why they are failing. Go is not my strong suit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking that up! There are a few things which need to be addressed.
Also the examples are missing (see the examples/
folder).
internal/provider/resource_gitlab_project_protected_environment.go
Outdated
Show resolved
Hide resolved
internal/provider/resource_gitlab_project_protected_environment.go
Outdated
Show resolved
Hide resolved
internal/provider/resource_gitlab_project_protected_environment.go
Outdated
Show resolved
Hide resolved
This pull request has merge conflicts. Please rebase your branch onto |
Conflicts are resolved. Thank you! 😀 |
internal/provider/resource_gitlab_project_protected_environment.go
Outdated
Show resolved
Hide resolved
internal/provider/resource_gitlab_project_protected_environment.go
Outdated
Show resolved
Hide resolved
internal/provider/resource_gitlab_project_protected_environment_test.go
Outdated
Show resolved
Hide resolved
internal/provider/resource_gitlab_project_protected_environment_test.go
Outdated
Show resolved
Hide resolved
internal/provider/resource_gitlab_project_protected_environment_test.go
Outdated
Show resolved
Hide resolved
internal/provider/resource_gitlab_project_protected_environment_test.go
Outdated
Show resolved
Hide resolved
internal/provider/resource_gitlab_project_protected_environment_test.go
Outdated
Show resolved
Hide resolved
@armsnyder @timofurrer Not sure if there is a way to mark me permanently as a trusted contributor for this PR but for protected environments I do not have an EE license to test with and I have to do the functional tests for them. If you have a temp license or another way to do the tests I am all ears |
@Shocktrooper Unfortunately, we can't I'm afraid - Good news though is that you can obtain a free Ultimate license as a trial, from here: https://about.gitlab.com/free-trial/. |
@timofurrer Perfect ty! |
@timofurrer I am also completely re-hauling the protected environments acceptance tests based on review comments on the project environments resource and other things. I should have it done later today |
@Shocktrooper sounds good! I've assigned it to the next release, which I plan to release shortly after GitLab 14.9 is out :) I'm going to review it in the evening :) Just re-request the review once you are done 🎉 |
@timofurrer Will do! Also want to get these 2 fields you added in assuming the go-gitlab work is done and released before 14.9? https://gitlab.com/gitlab-org/gitlab/-/merge_requests/82980 |
These two fields are already present in the responses of 14.8 - but just weren't documented. However, they are not yet in go-gitlab and I don't think they are of particular interest - at least not in this first iteration of these resources. I'd ignore them for now :) |
@timofurrer Sounds good! Also I have to go back to bed but I believe the acceptance tests are close to a done state pending any failures if you want to take a cursory check. I'll fix any review comments/failures in ~5 hours when I wake up. |
@Shocktrooper I'm actually working on a few shortcomings and fixing the tests. I'll keep you posted :) |
Alright @Shocktrooper I did couple of things here:
The tests should now pass and as far as I can tell the resource work fine :) I'd say this is ready for a merge. Because I've changed quite some stuff I'd be happy if @armsnyder you can review :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🎉
@armsnyder WDYT ? 🏓
@timofurrer Want to resolve all of the pending threads as well? |
@Shocktrooper Yes, absolutely - I thought I did but obviously wasn't the case 🤦 |
This functionality has been released in v3.13.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! |
Continuation of #750 on a new fork