When using the minimal terraform example in the readme that leverages the metaflow terraform module, terraform apply surfaced tags that were not in terraform plan.
Here's an example output:
Error: Provider produced inconsistent final plan
When expanding the plan for module.metaflow.module.metaflow-metadata-service.aws_ecs_cluster.this to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for .tags_all: new element "Metaflow" has appeared.
This is a bug in the provider, which should be reported in the provider's own issue tracker.
Error: Provider produced inconsistent final plan
When expanding the plan for module.metaflow.module.metaflow-metadata-service.aws_ecs_cluster.this to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for .tags_all: new element "Name" has appeared.
This is a bug in the provider, which should be reported in the provider's own issue tracker.
Error: Provider produced inconsistent final plan
When expanding the plan for module.metaflow.module.metaflow-metadata-service.aws_ecs_cluster.this to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for .tags_all: new element "managedBy" has appeared.
This is a bug in the provider, which should be reported in the provider's own issue tracker.
Error: Provider produced inconsistent final plan
When expanding the plan for module.metaflow.module.metaflow-datastore.aws_db_subnet_group.this to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for .tags_all: new element "Metaflow" has appeared.
This is a bug in the provider, which should be reported in the provider's own issue tracker.
Error: Provider produced inconsistent final plan
When expanding the plan for module.metaflow.module.metaflow-datastore.aws_db_subnet_group.this to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for .tags_all: new element "Name" has appeared.
This is a bug in the provider, which should be reported in the provider's own issue tracker.
Error: Provider produced inconsistent final plan
When expanding the plan for module.metaflow.module.metaflow-datastore.aws_db_subnet_group.this to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for .tags_all: new element "managedBy" has appeared.
When using the minimal terraform example in the readme that leverages the metaflow terraform module, terraform apply surfaced tags that were not in terraform plan.
Here's an example output: