microservice config management, centralized or distributed

Hey folks, I'm wrestling with how to best manage configuration for a growing microservices architecture. We've got a few different ideas floating around. One camp wants a single, centralized configuration server (like Spring Cloud Config or Consul). The other camp prefers each service to manage its own config, maybe with a shared library or even GitOps. What are your experiences? Do you have a preferred approach for keeping configs consistent and manageable across many services, especially when dealing with different environments (dev, staging, prod)