You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, We had a working pipeline that stopped functioning this week.
This is the error message that we see every time the pipeline runs. Can you please help?
Let me know any more details are needed
module.tf_next.module.statics_deploy.aws_sqs_queue_policy.this: Refreshing state... [id=https://sqs.us-east-1.amazonaws.com/444178128113/tf-next-web-site2022062411521676860000000a]
╷
│ Error: Invalid function argument
│
│ on .terraform/modules/tf_next/main.tf line 4, in locals:
│ 4: config_file = jsondecode(file("${local.config_dir}/config.json"))
│ ├────────────────
│ │ while calling file(path)
│ │ local.config_dir is "./.next-tf"
│
│ Invalid value for "path" parameter: no file exists at
│ "./.next-tf/config.json"; this function works only with files that are
│ distributed as part of the configuration source code, so if this file will
│ be created by a resource in this configuration you must instead obtain this
│ result from an attribute of that resource.
The text was updated successfully, but these errors were encountered:
Hi, We had a working pipeline that stopped functioning this week.
This is the error message that we see every time the pipeline runs. Can you please help?
Let me know any more details are needed
module.tf_next.module.statics_deploy.aws_sqs_queue_policy.this: Refreshing state... [id=https://sqs.us-east-1.amazonaws.com/444178128113/tf-next-web-site2022062411521676860000000a]
╷
│ Error: Invalid function argument
│
│ on .terraform/modules/tf_next/main.tf line 4, in locals:
│ 4: config_file = jsondecode(file("${local.config_dir}/config.json"))
│ ├────────────────
│ │ while calling file(path)
│ │ local.config_dir is "./.next-tf"
│
│ Invalid value for "path" parameter: no file exists at
│ "./.next-tf/config.json"; this function works only with files that are
│ distributed as part of the configuration source code, so if this file will
│ be created by a resource in this configuration you must instead obtain this
│ result from an attribute of that resource.
The text was updated successfully, but these errors were encountered: