Unable to use project factory yaml within folder hierarchy

[derailed-dash]

I've been trying to use the project-factory as described here.

I have created a folder hierarchy, with the structure:
/data/hierarchy/tnt-foo

Within my tnt-foo folder, I have a defined a project yaml called prj-foo-app-1.yaml:

# project prj-foo-app-1
labels:
 app: app-1
 team: foo
services:
  - container.googleapis.com
  - storage.googleapis.com
service_accounts:
  app-1-be:
    display_name: "Foo app 1 backend."
    iam_self_roles:
    - roles/logging.logWriter
    - roles/monitoring.metricWriter
    iam_project_roles:
      my-host-project:
        - roles/compute.networkUser
  app-1-fe:
    display_name: "Foo app 1 frontend."
    iam_project_roles:
      my-host-project:
        - roles/compute.networkUser
billing_budgets:
  - billing-20

When I run my terraform plan, the project to be created correctly detects that its parent is tnt-foo. But the Terraform then fails, because the project module expects the parent to always be of the form "folders/folder_id" or "organizations/organization_id". (See .terraform/modules/project-factory/modules/project-factory/main.tf line 24, in module "projects".)

The examples indicate that it should be possible to specify a parent in this format, e.g.

parent: bar/baz

Of course, at runtime, the folder ID of the newly created folder is not yet known. So I need to either determine the newly created folder ID at runtime, or the Terraform needs to work with a parent folder name, rather thn a folder ID.

Please can you help?

[derailed-dash]

Actually, I think this was user-error on my part. My _config.yaml was at the wrong level in my hierarchy! I moved it to where it should be, and the error has disappeared. Sorry!!