Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
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
general
Title
g
gorgeous-minister-41131
01/24/2023, 6:23 PMIs anyone using Pulumi in an ArgoCD workflow? e.g. generating manifests using the k8s YAML provider, then either feeding them or comitting them for ArgoCD to pick up for GitOps?
One thing that I am thinking of that is problematic, that isn't an issue with say, helm template, is that Pulumi wants to track the state of the stack. This is to be expected, that's Pulumi's whole point. Is there an easy way in Pulumi to suppress the state tracking and only use the stack config for configurations? e.g. if I'm using the
render_yaml_to_directoryg
gorgeous-egg-16927
01/26/2023, 3:54 PMhttps://github.com/pulumi/pulumi-kubernetes/issues/1468#issuecomment-777682678 has some info about this.
g
gorgeous-minister-41131
01/26/2023, 9:28 PMHey @gorgeous-egg-16927 thanks for this information. It's what I'm actually kinda working on is just using a local backend that is using
mktemp -de
early-cat-34152
01/27/2023, 11:18 AMWhy would the state tracking need to be suppressed, rather than disposed?