Hello I tried to apply <metaflow.tf> to our own in...
# ask-metaflowc
crooked-camera-86023
08/29/2025, 10:51 PMHello I tried to apply metaflow.tf to our own internal infra, and I got the following error and really appreciate any pointer/help.
crooked-camera-86023
08/29/2025, 10:54 PMAnd here is the error:
Copy code
│ Warning: Argument is deprecated
│
│ with module.metaflow.module.metaflow-datastore.aws_s3_bucket.this,
│ on .terraform/modules/metaflow/modules/datastore/s3.tf line 1, in resource "aws_s3_bucket" "this":
│ 1: resource "aws_s3_bucket" "this" {
│
│ Use the aws_s3_bucket_server_side_encryption_configuration resource instead
│
│ (and one more similar warning elsewhere)
╵
╷
│ 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
│ "<http://registry.terraform.io/hashicorp/aws|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
│ "<http://registry.terraform.io/hashicorp/aws|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.
╵crooked-camera-86023
08/29/2025, 10:54 PMBTW, i was simply following the example in https://registry.terraform.io/modules/outerbounds/metaflow/aws/0.3.0
h
hundreds-zebra-57629
08/29/2025, 11:18 PMAre you following one of the example here? If so which one? Looks like you may have a more recent aws provider installed.
👀 1
c
crooked-camera-86023
08/29/2025, 11:54 PMThanks for the pointers. I think one of the issue is that we have a higher version of terraform for our internal infra.
crooked-camera-86023
08/31/2025, 7:08 PMCan we upgrade the examples to work with more recent version of terraform. I ran into various issues with the latest terraform, like:
Copy code
1. <http://argo.tf:2|argo.tf:2> - helm provider kubernetes should use = not block syntax
2. EKS module still has the elastic_inference_accelerator compatibility issue
The <http://argo.tf|argo.tf> file was reverted. Need to fix the helm provider syntax again.
⏺ Update(<http://argo.tf|argo.tf>)
⎿ User rejected update to <http://argo.tf|argo.tf>
1 provider "helm" {
2 - kubernetes {
2 + kubernetes = {
3 host = data.aws_eks_cluster.cluster.endpoint
4 cluster_ca_certificate =
base64decode(data.aws_eks_cluster.cluster.certificate_authority.0.data)
5 token = data.aws_eks_cluster_auth.cluster.token