Daniel Ferreira

> Hi @daniel-anova, thanks for reporting this error. How many group members are you adding and to how many groups? Were the groups created as part of the same apply...

I can also add that if there's a large number of resources already in state even small additions seem to trigger the issue. Such has adding a dozen of memberships...

> Thank you for your input, @simongottschlag and @xuzhang3. > > Unfortunately I haven't received any feedback whatsoever, on the [Add new taskagent resource functionality #90](https://github.com/microsoft/azure-devops-go-api/issues/90) issue/feature request. So an...

> @daniel-anova - thanks for reporting this issue! Can you let me know what is the reason your sensor spec gets so large? We're using argo to schedule data processing...

comment to keep this issue alive.

> Hey @daniel-anova, thanks for reporting. Can you please check that you can download version `0.25.0`? > > https://artifacthub.io/packages/helm/grafana/tempo-distributed Yes, version 0.25.0 is showing.

Also, version 0.24.2 is also showing, so seems whatever happened with 0.24.1 was a one-off issue?

> Could you let us know what version of Flux is installed? > > I'm looking at this issue and it reminds me of an issue that affected Flux's "new"...

The HelmRelease was correct with both `kubectl` and Kustomize controller, I just retested the test case to be 100% sure and when removing the duplicate value the `HelmRelease` shows the...

Hitting the same issue, when upgrading to azurerm 3.15.1, the plan shows it wants to remove the value and then add it again (which is not allowed). I initially thought...