sparse-intern-71089
04/14/2022, 8:55 PMminiature-musician-31262
04/14/2022, 8:58 PMminiature-musician-31262
04/14/2022, 9:03 PM➜ example tree .
.
├── infra
│ ├── Pulumi.dev.yaml
│ ├── Pulumi.yaml
│ ├── index.ts
│ └── package.json
└── my-app
├── package.json
└── src
miniature-musician-31262
04/14/2022, 9:03 PMfull-king-49894
04/14/2022, 9:04 PMminiature-musician-31262
04/14/2022, 9:04 PMfull-king-49894
04/14/2022, 9:05 PMinfra
any sort of convention? I prefer to adopt existing conventions than create my own taxonomyminiature-musician-31262
04/14/2022, 9:06 PMinfra
and infrastructure
are common choices for these, i’d say, yeahfull-king-49894
04/14/2022, 9:06 PMminiature-musician-31262
04/14/2022, 9:06 PMfull-king-49894
04/14/2022, 9:07 PMagreeable-eye-87399
04/15/2022, 12:58 AMrhythmic-branch-12845
04/15/2022, 12:59 AMagreeable-eye-87399
04/15/2022, 1:02 AMpulumi up
Now…you can have more than one project per repo - there is nothing explicitly tying project to repo…
Think about it this way. The “project” is everything ar the same level as Pulumi.yaml, which includes the program. The program is the entry point (main.go, index.ts, etc)
I think I said all this right. But @miniature-musician-31262 can and will correct me :)full-king-49894
04/15/2022, 2:29 PMagreeable-eye-87399
04/15/2022, 2:37 PMfull-king-49894
04/15/2022, 2:41 PMagreeable-eye-87399
04/15/2022, 2:42 PMagreeable-eye-87399
04/15/2022, 2:45 PM