Hi Team! I just got started with Pulumi this week...
# automation-api
t
Hi Team! I just got started with Pulumi this week and it looks really promising! I want to manage a stack with both Automation API and via GitOps (e.g. the stack's config should be stored somewhere, probably Git) - how can I reconcile these two ways of managing the stack? • The workflow I'm imagining: the automation API updates the stack with some config supplied by a user. I want that config to persist somewhere so these changes won't get overridden when we update the stack via GitOps flow. • Am I using Pulumi correctly? Is there a better way to do this?