This message was deleted.
# atlantis-community
s
This message was deleted.
j
works fine, except if you make a change to
values.yaml.tpl
since its not a .tf file its ignored. But if you add those files to the autoplan, atlantis attempts to run terraform from within the
templates
directory, which also is not correct.
p
do you have a project defined?
j
The only thing defined, is a
repoconfig
Copy code
repoConfig: |
 ---
 repos:
 - id: /.*/
   apply_requirements: [mergeable]
   import_requirements: [mergeable]
p
I think you need a project define where you define the dir and autoplan so that it always uses that dir instead
j
I do not think that would work
we are in a mono repo.
breaking it out, makes Atlantis not really worth the investment
p
I have a monorepo but I define all projects dynamically
j
so we look like this..
Copy code
  ~/trex/trex_ops_infra   dev_cw_prio *1                                                                                                                                                                                     01:17:55 PM
❯ tree -L 2
.
├── bastion-config
├── dev
│   ├── atlantis
│   ├── cluster
│   ├── core-applications
│   ├── gitlab
│   ├── jenkins
│   ├── network
│   └── vault
├── Pipfile
├── Pipfile.lock
├── prod
│   ├── acm
│   ├── atlantis
│   ├── cluster
│   ├── core-applications
│   ├── gitlab
│   ├── jenkins
│   ├── network
│   └── vault
├── remote_access.md
└── ssh-ssm.sh
but some of those folders, have sub-folders as well
so im not sure how we would define that
w
one way, if I’m understanding the question correctly and you’re using a repo config:
Copy code
projects:
  - dir: dev/atlantis
  - dir: dev/cluster
[...]
  - dir: prod/acm
[...]
  - dir: prod/gitlab/some/other/state
j
@PePe Amengual care to elaborate on how you do it, dynamically? because writing it all out like the above would be a lot of effort. Since some of those folders are layers deep.
one way of doing it
using pre_workflow_hooks
you can run any script to generate your atlantis.yaml