Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Powered by
Title
a
ambitious-agent-35343
08/17/2022, 8:02 AM
Do people keep their infrastructure as code with their application or in a separate infrastructure repo?
v
victorious-wall-1075
08/17/2022, 8:07 AM
We have created a python library over pulumi and use the library in our application). The library is in our repository . [we are using python3]
👍 2
a
ambitious-agent-35343
08/17/2022, 8:08 AM
Interesting, is this standard practice?
f
few-processor-89505
08/17/2022, 8:09 AM
.Net land here. We have projects in the same repo but not opened in the same solution. So same repo but code is separate
d
damp-honey-93158
08/19/2022, 6:19 AM
We created a library with useful functions / ideas in it and make it available to devs, as a way to wrap up the complexity. Still early stages for us.
And we also find that its really useful to throw infra code into the same repo as the application in addition to the C# library we created.
3 Views
#general
Join Slack