// the find
dyc87112/spring-cloud-config-admin
Spring Cloud Config的综合管理后台（简称：SCCA）
A web admin console for Spring Cloud Config Server, so you manage config properties through a UI instead of hand-editing files in Git or rows in a database. It covers environments, per-environment parameters, encrypted values, projects and versions, with Git or database storage and Eureka or Consul for discovery. It is aimed at teams already running Spring Cloud Config who want an editor on top of the storage backend.
- Each backend is a separate module (scca-persistence-git, scca-persistence-db, scca-discovery-eureka, scca-discovery-consul) wired in through spring.factories, so you choose storage and discovery by adding a dependency rather than forking the project.
- Encryption is a built-in feature, with encrypt and decrypt operations and batch encryption of selected parameters. Most teams otherwise script this against the config server's encrypt endpoint.
- Per-environment parameters and batch placeholder replacement across environments target the usual dev, staging and prod copy-paste problem. The same config can be edited as a list, as YAML or as properties.
- The last push was June 2022 and the 1.2.0 section still says in development, so treat this as a snapshot. Confirm it builds and runs on your current Spring Boot and Spring Cloud versions before you plan around it.
- The UI lives in a separate repository (spring-cloud-config-admin-web), so you deploy and version two projects. The README gives no compatibility matrix between backend and frontend releases.
- Access control is local user accounts with roles and a permission matrix. The README says nothing about SSO or LDAP, so enterprise identity integration would be your work.