I'm looking into the CI/CD process to deploy new & update workflows. A few questions: • When I update the deployment setup from the UI (like tags, schedules...) where is the updated info stored? Is it possible to sync it back to the original YAML file? • Follow up from the first point. If a deployment with

name_a

already existed with some modified configs, and now I run

deployment apply

on the same original deployment file, I will lose all of the configs. Is there any way to avoid this, or what's the best practice when handling deployments?

the info is stored on the backend whether you create/modify/delete deployment info from the CLI, UI or Python client code, it triggers an API code that makes the changes in the backend you shouldn't worry about the files too much

Thanks Anna. I want to version-control everything relating to deployments, so I think it would be nice to be able to sync the deployment configs back to the file. I agree that being able to modify certain configs in the UI is very convenient, but as I mentioned above, if I accidentally re-apply a yaml deployment file with out-of-date config ( comparing to the backend) then I will lose the backend config

Don't worry as much about YAML, it's really a build artifact