Is it possible to structure a project like this? `...
# general
b
Is it possible to structure a project like this?
Copy code
./
  - Pulumi.yaml
  - production/
      - Pulumi.production.yaml
      - ...
  - dev
      - Pulumi.dev.yaml
      - ...
c
Yes, you can use the
--config-file
CLI flag when calling pulumi, or specify
stackConfigDir
in Pulumi.yaml
My preference is to set
stackConfigDir: stacks
then put all the environment config files under a single stacks/ directory
b
Maybe I'm missing something, but
--config-file
doesn't seem to be doing what I'm looking for. I don't see how
stackConfigDir
would help here either, as I don't want all my stack config in one directory. I was hoping to get every stack in its own directory.
c
--config-file
lets you specify where your config file is, when you invoke pulumi though?