I have a bunch of production services set up for running my web app (worker, database, redis etc), all of which have been created and configured via the Web UI.
Now I would like to start using preview environments. I am looking at adding a
render.yaml file to my project, so that I can create a bunch of connected services that will spin up/spin down when PRs are created/merged.
My question is about the relationship between my active services (database, redis etc) that are running in production, and the
render.yaml blueprint file. From the docs it seems like the
render.yaml file will be ignored unless I specifically create a “New Blueprint Instance” from the render.com dashboard. Is that the case?
If so, then it seems like so long as I keep managing my production services via the Web UI, I can safely write whatever I want in the render.yaml file, and it will be ignored by all my production instances. The file will only be used by preview environments. Is that correct?