-
Notifications
You must be signed in to change notification settings - Fork 77
Frequent 404s on "gsuite_group_member" #90
Comments
gsuite_group_member
possible gsuite API bug/behavior? In this case... perhaps adding a |
We've been adding retries to a bunch of things on 404's, but it slows down everything else. #53
Did we verify it's not this? I don't think there is pagination in the way here. |
I'm not sure exactly when, but I've noticed this issue has completely gone away sometime over the past 4-8 weeks. I've updated to the latest release a few times over that span so I'm not sure which version did it but it is working quite well now. |
Just encountered this again. I guess it hasn't been resolved. |
I'm facing this as well. I did try to set the The amusing part is that the group was created and all other members were part of it, only one member could not be added somehow. Adding it manually made it work (but clearly is not a good/tenable solution). |
Are the members being added external to the domain? Is the error message still exactly the same? I haven't seen it for quite a while, and use the provider extensively. |
@DeviaVir sorry for the delay, the notification must have slipped through the cracks. |
Hi @DeviaVir Is there any progress on this issue? we are using the provider:
and trying to add a member to a group via the resource
|
Another update from my side. We have a other gsuite group within the group I want to add members to. The member I want to add is already within the group in the group. so Which - of course - will fail as the member is not a direkt member of the gsuite group but is only a member of the sub-group. Edit:
|
Occasionally I will get 404s when attempting to add a group member that is definitely a valid address in the gsuite domain. In fact... I may be able to add that address just fine to one group but it will fail on others in the same terraform run.
Here is a typical response:
Meanwhile... that very same member was added to the
prod
group without issue.My intuition say it might be an issue with the pagination of results. That could definitely explain intermittent 404s. I'm not seeing anything obvious in a
TF_LOG=debug
run either.If I manually add the user in the web console and re-run, the errors goes away.
The text was updated successfully, but these errors were encountered: