Skip to content
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

datasource: gitlab_projects #279

Merged
merged 1 commit into from
May 30, 2020
Merged

datasource: gitlab_projects #279

merged 1 commit into from
May 30, 2020

Conversation

oboukili
Copy link
Contributor

@oboukili oboukili commented Mar 14, 2020

Picked up the work of https://github.com/terraform-providers/terraform-provider-gitlab/pull/161, as this is a critical missing datasource.

  • Made group_id optional
  • Use terraform-plugin-sdk
  • Method refactoring here and there

Most credit goes to @enieuw and the original PR contributors.

EDIT: I ended up redoing everything after all, the datasource now supports fully all group and project listProject APIs parameters exposed by the go-gitlab package.

@RyPeck
Copy link
Contributor

RyPeck commented Mar 16, 2020

Much appreciated - I currently use an external provider to retrieve the list of project_ids in a given group that I want to manage.

@oboukili
Copy link
Contributor Author

I still do not understand why the acceptance tests I added detect a state drift, I guess I'll have to read the docs more thoroughly, any help would be appreciated!

@oboukili
Copy link
Contributor Author

oboukili commented Mar 28, 2020

@roidelapluie I would definitely love having your input on datasources state drift resolution, I could not make it work.

EDIT: so I got it, it seems using explicit depends_on on a datasource does not prevent the related state object to exist, albeit empty, and therefore cause a false state drift detection. Anyways that's how I understand it, it was really informative :)

@oboukili
Copy link
Contributor Author

oboukili commented Apr 1, 2020

Ready for review, this is essentially done.

@oboukili
Copy link
Contributor Author

oboukili commented Apr 4, 2020

Pinging @ringods if I can do anything else to make this PR merged, please let me know, cheers :)

@ringods
Copy link
Contributor

ringods commented Apr 4, 2020

@oboukili FYI: https://github.com/terraform-providers/terraform-provider-gitlab/issues/133#issuecomment-607454848

@oboukili oboukili force-pushed the master branch 2 times, most recently from 4d3af60 to cd2c249 Compare April 8, 2020 17:12
@oboukili
Copy link
Contributor Author

Hey there, any chance for a review?

@thapakazi
Copy link

What's required to get this merged ??

@ringods
Copy link
Contributor

ringods commented May 27, 2020

Hello @oboukili & @thapakazi, I became a maintainer of this provider not so long ago. I'm going over the pull requests backlog one by one.

Yesterday, I merged in another PR. While the PR build results were succesful, after merging, the commit on master failed. I reached out to the PR author to see if there is a correlation with the changes from the PR.

https://github.com/terraform-providers/terraform-provider-gitlab/runs/710870254

I hope you understand that I want to see the master branch have "green" tests first.

@thapakazi
Copy link

Totally understandable 👍 , anything we can help you up with?

@ringods
Copy link
Contributor

ringods commented May 28, 2020

@oboukili & @thapakazi the master branch is "green" again. I ran through this PR again.

May I ask to rebase your PR, meanwhile also squashing some commits?

The current list of commits is quite extensive and I'm not sure it adds to the clarity.

@ringods ringods merged commit 485ab3a into gitlabhq:master May 30, 2020
@ringods
Copy link
Contributor

ringods commented May 30, 2020

Tnx for your contribution. I will try to get this in a release later this week.

@oboukili
Copy link
Contributor Author

Awesome, many thanks for the review @ringods !

@ringods
Copy link
Contributor

ringods commented Jun 2, 2020

Released in v2.9.0

ahmet2mir pushed a commit to ahmet2mir/terraform-provider-gitlab that referenced this pull request Sep 15, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Nov 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

Successfully merging this pull request may close these issues.

4 participants