You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.
No-op. This destructive behavior is really unfriendly and leads to operational surprises and problems. initial group config should have no bearing on existing groups.
Actual Behavior
Groups were destroyed and re-created as described in #9035
google_cloud_identity_group.my_group must be replaced
...
+ initial_group_config = "EMPTY" # forces replacement
ajlake
changed the title
new google_cloud_identity_group.initial_group_config flag triggers recreate of existing groups
google_cloud_identity_group.initial_group_config flag triggers recreate of existing groups
May 12, 2021
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
0.14.6
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
No-op. This destructive behavior is really unfriendly and leads to operational surprises and problems. initial group config should have no bearing on existing groups.
Actual Behavior
Groups were destroyed and re-created as described in #9035
Steps to Reproduce
my_group
using provider version <= 3.66.1Observe create/destroy of group.
References
The text was updated successfully, but these errors were encountered: