Open jazzlyn opened 2 years ago
workaround
lifecycle {
ignore_changes = [
email
]
}
Hi @jazzlyn, thanks for raising this issue and showing a workaround for others who might have the same issue!
I've found that the underlying cause is that the 2 APIs used to manage Groups (Directory API) and Group Settings (Group Settings API) handle the group's email differently. When groups are made the email is automatically converted to lower case. Group settings are made using the original email with upper case characters, which happens behind the scenes on Google's backend when new groups are made. This mismatch of emails using/not using upper case characters causes issues, and there's no way for the provider to update the group settings to use the lower case email.
As the root cause is inconsistent handling of capitalisation by Google's APIs I'd recommend avoiding putting capital letters in the groups email
value. I'm working on a solution for this issue but avoiding it is best, given the restrictions on what the provider can control.
Saw this as well, but after destroying and making sure group name was lower case it appears to be fine. I orginally had the name of the group and email in UPPER case.
@SarahFrench any chance that this provider can be adopted by someone still working for hashicorp?
workaround
lifecycle { ignore_changes = [ email ] }
@jazzlyn which resource did you put the lifecycle rule in as I am not having any success with that as a workaround.
@security-penguin to resource "googleworkspace_group_settings"
Hi there,
Terraform Version
Terraform v1.2.1 on linux_amd64
Affected Resource(s)
Configuration
Group configuration:
Output