Timo Furrer

Yes, it's what I suspected, too. It goes into the same direction of https://gitlab.com/gitlab-org/gitlab/-/issues/352299

I've seen it happening twice here on GitHub - and never locally. I'm removing the `p1` label and let's not rush this as it really seems to be rare ...

Does this also happen for you without the `for_each`, basically for a single group variable?

Okay, I'll dig into that later ... Out of curiosity: does it also happen without the environment scoping? On Thu, Feb 10, 2022, 6:15 PM Liberis ***@***.***> wrote: > I...

@Liberis I'm still unable to reproduce this. What responses do you get from the API calls you posted. Creating a simple non-protected / non-masked variable with an environment scope: ```...

Alright, I can reproduce if two environments have the same `variable` - you can actually create them, but not update. Just to confirm? Do you have variables with the same...

Properly setting the filter in the `PUT` call, helps, e.g.: ``` curl -g -X PUT "http://localhost:8080/api/v4/groups/108/variables/some_protected_var?filter[environment_scope]=env" --header "PRIVATE-TOKEN: ACCTEST1234567890123" --form "value=blabla" ```

I see, @Liberis ... can you please try and use the latest provider version >= 3.9.0 ? Support for the *environment scope* for `gitlab_group_variable`s has been added in https://github.com/gitlabhq/terraform-provider-gitlab/releases/tag/v3.9.0 (see...

I can reproduce it now, thanks for the report - I'll get back to you. There are definitely some interesting issues open in go-gitlab: * https://github.com/xanzy/go-gitlab/issues/746

After some debugging it seems to be an upstream issue: https://gitlab.com/gitlab-org/gitlab/-/issues/333296 I'm afraid we can't do much here.