dwilliams782

-----------------------------------------------------: timestamp=2022-02-23T12:30:34.942Z
2022-02-23T12:30:34.942Z [INFO]  plugin.terraform-provider-googleworkspace: 2022/02/23 12:30:34 [DEBUG] Retry Transport: Stopping retries, last request was successful: timestamp=2022-02-23T12:30:34.942Z
2022-02-23T12:30:34.942Z [INFO]  plugin.terraform-provider-googleworkspace: 2022/02/23 12:30:34 [DEBUG] Retry Transport: Returning after 1 attempts: timestamp=2022-02-23T12:30:34.942Z
2022/02/23 12:30:34 [WARN] Provider "registry.terraform.io/hashicorp/googleworkspace" produced an invalid plan for module.all_engineering.module.google_group.googleworkspace_group_member.user["<email-removed>"], but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
-       .timeouts: planned for absense but config wants existence
2022-02-23T12:30:34.954Z [INFO]  plugin.terraform-provider-googleworkspace: 2022/02/23 12:30:34 [DEBUG] 

dwilliams782

#! /bin/bash
set -eou pipefail

if [[ -z ${1+x} || ${1} == "all" ]]; then
  echo "Checking all namespaces"
  namespaces=$(kubectl get namespaces -o json | jq -r '.items[].metadata.name')
else
  namespaces=${1}
fi

dwilliams782

module.digital_product.module.sub_google_group["Manage"].googleworkspace_group_settings.group-settings: Destroying... [id=_gcp.manage.team@<domain>.com]
2021-07-13T18:31:33.147+0100 [INFO]  plugin.terraform-provider-googleworkspace_v0.3.0_x5: 2021/07/13 18:31:33 [DEBUG] Removing Group Settings from state for "_gcp.manage.team@<domain>.com": timestamp=2021-07-13T18:31:33.147+0100
module.digital_product.module.sub_google_group["Manage"].googleworkspace_group_settings.group-settings: Destruction complete after 0s
2021/07/13 18:31:33 [WARN] Provider "registry.terraform.io/hashicorp/googleworkspace" produced an invalid plan for module.digital_product.module.sub_google_group["Manage"].googleworkspace_group_settings.group-settings, but we are tolerating it because it is using the legacy plugin SDK.
The following problems may be the cause of any confusing errors from downstream operations:
- .reply_to: planned value cty.StringVal("REPLY_TO_IGNORE") does not match config value cty.NullVal(cty.String)
- .include_custo