Timo Furrer

Not that I know of. If anyone wants to start with this, please keep the following topics in mind: https://github.com/gitlabhq/terraform-provider-gitlab/issues/869 #1058

@ftpd Could you please run the `terraform apply` with `TF_LOG=debug` to see the request made to GitLab - and please redact the output to not leak any secrets ;) -...

@ftpd sorry my bad 🤦 I'll dig into this a little bit more in depth later. For now, the `active` field looks suspicious .. it's an optional field which activates...

Just saw in the response that it's actually active 🤔

> Any advices welcomed, anyway. I think it makes sense to open an issue here: https://gitlab.com/gitlab-org/gitlab/-/issues @valvin1 any more information from your side?

I'm still trying to understand what exactly is going on here. I wonder why it tries to re-create the approval rule. I assume that you've first run your terraform, then...

Yes, I think I agree there with @jtymes. You need to import first and the read (during plan) isn't aware of the id conflict there ...

@jtymes sounds great! > It looks like there may need to be some modifications to GitLab's API exposure as well to reach parity with the UI options, but I think...

Correct me if I'm wrong, but I think @jtymes already start working on this :)

@bgadberry-gitlab @nagyv I'll take care of this and if all goes well it'll be available in the next provider release shortly after 15.3 has been released ;)