Put me out of my misery with Fabric deployment pipelines

We're trying to move off doing everything manually in the browser and actually get a proper dev/test/prod setup going for our Fabric workspace. the git integration part was fine, connected the workspace to a repo, branching works, that side makes sense. where it's falling apart is the actual promotion between stages. Notebooks and Spark job definitions move through the deployment pipeline cleanly. Anything with a connection string or workspace specific parameter doesn't carry over the way I expected, so after every deploy I'm going in by hand and fixing things that should've just mapped over.