resource "prefect_flow" "base_flow" {
  name         = "my-example-flow"
  workspace_id = local.prefect_workspace_id
  tags         = []
  account_id   = local.prefect_account_id
}


resource "prefect_deployment" "base_deployment" {
  name         = "stg--pipeline-testing"
  flow_id      = prefect_flow.base_flow.id
  entrypoint   = "pipeline-testing/main.py:root"
  workspace_id = local.prefect_workspace_id
  account_id   = local.prefect_account_id

  paused = false
  pull_steps = [
    {
      type      = "set_working_directory",
      directory = "/opt/prefect/pre",
    }
  ]

  job_variables = jsonencode({
    "image" : "{mask}.<http://dkr.ecr.us-east-1.amazonaws.com/ml-mono/test/prefect:v1.2.3|dkr.ecr.us-east-1.amazonaws.com/ml-mono/test/prefect:v1.2.3>"
  })

  work_pool_name  = prefect_work_pool.pipeline_work_pool.name
  work_queue_name = "default"

  depends_on = [
    prefect_work_pool.pipeline_work_pool
  ]
}

Plan: 1 to add, 1 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

prefect_flow.base_flow: Modifying... [id=2e70432a-5b85-440a-80f6-d2b5833312d1]
╷
│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to prefect_flow.base_flow, provider "provider[\"<http://registry.terraform.io/prefecthq/prefect\|registry.terraform.io/prefecthq/prefect\>"]"
│ produced an unexpected new value: .account_id: inconsistent values for sensitive attribute.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
mac:stg destefano$

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 4.0"
    }
    prefect = {
      source  = "prefecthq/prefect"
      version = "2.17.1"
    }
  }
}

provider

terraform destroy

account_id

workspace_id

provider