Channels
welcome
pulumi-cdk
cloudengineering
yaml
blog-posts
localstack
pulumi-ai
package-authoring
general
pulumiup-booth-support
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
gitlab
pulumi-kubernetes-operator
jobs
pulumi-deployments
dotnet
aws
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
Powered by
#general
Title
l
limited-rainbow-51650
06/11/2019, 6:58 PM
Are there already best practices to structure Pulumi code? Do we need multiple “stacks” like in TF land, using “remote state”? Any blog articles that could bootstrap me?
n
narrow-area-11460
06/11/2019, 7:05 PM
There are plenty of examples here:
https://github.com/pulumi/examples
and blogs here:
https://blog.pulumi.com/
if you want an example of referencing stacks in projects you can visually work with this blog:
https://blog.pulumi.com/continuous-delivery-with-gitlab-and-pulumi-on-amazon-eks
or refer to the documentation here:
https://pulumi.io/reference/organizing-stacks-projects/
👏🏼 1
c
chilly-crayon-57653
06/11/2019, 7:12 PM
I think this is a good link to get started ...
https://pulumi.io/reference/organizing-stacks-projects
👏🏼 1
Post