Patrick Rice

@timofurrer - Should we just update this to set the state on create/update, and skip import verification for now? It would require a separate attribute to change in order to...

@timofurrer - I updated the way this is handled to be set directly from the config on create/update, removed the suppress function and set the attribute as computed. I also...

@Shocktrooper - it is, but I know @timofurrer had some reservations with the approach

It looks like this will only impact hooks/integrations where the name is used instead of the ID, but then the ID is used to import the project. The import always...

I think we likely should open a design issue to figure out how we want to implement GraphQL. I haven't looked to see if there is a good library in...

Co-opting this issue a bit to mention that I've been looking at GraphQL clients "on the side", and there doesn't seem to be an _amazing_ option for how to proceed...

> There's also the option to not use any third party dependency Absolutely true. I'd say that if we're doing that, we should create a GitLab GraphQL Client project and...

> It almost feels like we would be rolling our own client library if we didn't do pure strings. I think we'd be rolling our own client regardless of whether...

I'm going to start working on a security policy resource using the GQL API here shortly, and I'll ping folks on this thread so we can talk strategy for how...

@armsnyder - I haven't created one yet, since I'm still trolling around a bit with the right approach. I did notice that issue, but thought it might be good to...