Hi guys, I am relatively new on IAC. I would wish to ask for opinions on the best practice to organize Pulumi projects. This link provides the best reference so far. However, I do not like the way that the app's main.go goes into the same repository with the other Pulumi code as it could reduce visibility.
I wonder it would be possible to place the app's main.go/index.ts together with the application code. I have an example in the picture attached.
This allows the pkg to be referenced from the service_api repo while having the visibility required.
Please feel free to comment on this structure.
04/05/2022, 8:46 PM
Yes, you can do it any way you like. There is no requirement to keep app code and deployment code together.
04/06/2022, 10:02 AM
If it's not clear on that page that the pulumi code can be separate from the application code, I'll make it more clear (I'm actually working in that page today lol)
Oh! I see - you're concerned about the monorepo approach. What I'm working on for that page today is an illustration of the microstacks pattern (which is the one you've illustrated above)