Atlantis doesn't respect child directories in project

[gartemiev]

I have a project in my repo which contains sub folders in addition. However After specifying that project on repocinfig level - Atlantis doesn't see any subprojects there:

running "/usr/local/bin/terraform plan -input=false -refresh -out \"/home/atlantis/.atlantis/repos/example/dev-infra/121/default/eu-central-1/infrastructure/infrastructure-default.tfplan\"" in "/home/atlantis/.atlantis/repos/example/dev-infra/121/default/eu-central-1/infrastructure": exit status 1
╷
│ Error: No configuration files
│ 
│ Plan requires configuration to be present. Planning without a configuration
│ would mark everything for destruction, which is normally not what is
│ desired. If you would like to destroy everything, run plan with the
│ -destroy option. Otherwise, create a Terraform configuration file (.tf
│ file) and try again.

Server side config:

repos:
  - id: bitbucket.org/example/dev-infra
    allow_custom_workflows: true
    allowed_overrides: [apply_requirements, workflow]

Repo config:

---
version: 3
projects:
- name: infrastructure
  dir: ./eu-central-1/infrastructure
  autoplan:
    when_modified:
      - "**/*.tf"
    enabled: true
  workflow: default

[jamengual]

remove the . / from. dir and see if it works

…

On Tue, Oct 18, 2022, 6:26 a.m. George Artemiev ***@***.***> wrote: I have a project in my repo which contains sub folders in addition. However After specifying that project on repocinfig level - Atlantis doesn't see any subprojects there: running "/usr/local/bin/terraform plan -input=false -refresh -out \"/home/atlantis/.atlantis/repos/openvpntechnologies/dev-infra/121/default/eu-central-1/infrastructure/infrastructure-default.tfplan\"" in "/home/atlantis/.atlantis/repos/openvpntechnologies/dev-infra/121/default/eu-central-1/infrastructure": exit status 1 ╷ │ Error: No configuration files │ │ Plan requires configuration to be present. Planning without a configuration │ would mark everything for destruction, which is normally not what is │ desired. If you would like to destroy everything, run plan with the │ -destroy option. Otherwise, create a Terraform configuration file (.tf │ file) and try again. Server side config: repos: - id: bitbucket.org/openvpntechnologies/dev-infra allow_custom_workflows: true allowed_overrides: [apply_requirements, workflow] Repo config: --- version: 3 projects: - name: infrastructure dir: ./eu-central-1/infrastructure autoplan: when_modified: - "**/*.tf" enabled: true workflow: default — Reply to this email directly, view it on GitHub <#2596>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ3ERDRNDTWUHIDOTWLDPTWD2QQVANCNFSM6AAAAAARICYWLU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[coetzeevs]

@gartemiev did you manage to solve this? I'm running into the same issue with nested folders. Trying to implement cdktf using Go.

[gartemiev]

@coetzeevs,

I've figured it out with the help of config generator for repository. So basically when Atlantis runs for repo - it runs a python script in my case inside which generates all projects paths to track:
`
projects:

• name: ./eu-central-1/infrastructure/elasticsearch/product_cluster/terraform
  dir: ./eu-central-1/infrastructure/elasticsearch/product_cluster/terraform
  apply_requirements: [approved]
  workflow: default
  autoplan:
  enabled: true
  when_modified:
  • '.tf'
• name: ./eu-central-1/infrastructure/pgmt-vpn/terraform
  dir: ./eu-central-1/infrastructure/pgmt-vpn/terraform
  apply_requirements: [approved]
  workflow: default
  `

But note: this requires customization of altantis image but it works perfectly. Something similar is already developed for Terragrunt case: https://github.com/transcend-io/terragrunt-atlantis-config

[coetzeevs]

Thanks for the response @gartemiev - in my case Atlantis didn't pick up the cdk.tf.json in the designated output dir (cdktf.out) to run the terraform commands against, so I kept getting this:

╷
│ Error: No configuration files
│ 
│ Plan requires configuration to be present. Planning without a configuration
│ would mark everything for destruction, which is normally not what is
│ desired. If you would like to destroy everything, run plan with the
│ -destroy option. Otherwise, create a Terraform configuration file (.tf
│ file) and try again.
╵

Once I moved the file out of that directory to the root for the repository the plan kicked off fine.