Hello again! I'm attempting to deploy multiple met...
# ask-metaflowf
faint-lion-81580
05/10/2023, 12:55 AMHello again! I'm attempting to deploy multiple metaflow stacks on GCP, as described here. Everything went smoothly, until setting up the kubernetes service account. The error looks like so. I am guessing that there is a clash because
default/metaflow-ksa Copy code
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to module.infra.google_service_account.metaflow_kubernetes_workload_identity_service_account, provider "module.infra.provider[\"<http://registry.terraform.io/hashicorp/google-beta\|registry.terraform.io/hashicorp/google-beta\>"]" produced an
│ unexpected new value: Root resource was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.u
user
05/10/2023, 5:05 PMAre you using TF workspaces to isolate the different MF stacks?
f
faint-lion-81580
05/10/2023, 6:04 PMyes.
faint-lion-81580
05/10/2023, 6:04 PMeach stack is in a different workspace.
faint-lion-81580
05/10/2023, 6:05 PMseparate issue - since it didn't work, tf destroy didn't remove the service accounts (per our previous thread on this - you were thinking that since these are global, tf doesn't know to destroy them.
u
user
05/10/2023, 6:52 PMOK I think might be related. I just shared an OB doc (not fully public) on how we use TF workspaces. https://docs.google.com/document/d/1QiLPoOfLmGtsWSBDEj0GIUVdnPXok1J6wyfm1TmFKkg/edit?usp=sharing. WE routinely maintain multiple stacks, tear them down, etc.
Could you take a look to see what operational differences there are vs what you are doing?
5 Views