Document How To Use GCP Secret Manager

Hi all, I appreciate the time and effort this team is taking to provide the support for this fantastic product. However, in one of my recent attempt to use spring-config-server with GCP Secret Manager is yielding no success. To get some much needed help, I am opening this discussion around it.

As per the Spring Cloud announcement here, I was expecting the GCP Secret Manager is supported. There are no docs around how to use the gcp-secret-manager backend (if there is any support). The official doc doesn't say much either.

I am running a simple config-server in GCP Cloud Run. I have to read some sensitive properties from a secret store like GCP Secret Manager (I am running apps in GCP Cloud Run) and some generic properties from a git backend. After multiple attempts, I am not able to get any success to read the configs from the secret manager using config-server. here is the application.yaml file for config server.

server:
  port: ${PORT:8080}
spring:
  application:
    name: config-server
  profiles:
    active: git, gcp-secret-manager
  cloud:
    config:
      server:
        gcp-secret-manager:
          application-label: application
          profile-label: profile
          token-mandatory: false
          order: 1
        git:
          uri: https://github.com/ichandan16/test-config-server.git
          order: 2

I have labeled my secrets as application: app1 and profile: dev. Trying to access cloud run config-server service with:
https://config-server-gcp-xxxxx-uw.a.run.app/app1/dev. I can read git backend data but not GCP secret manager.

Is there any document that you can help me with that gives a clear direction on how to use it.

/r,
Chandan Patra

Start with the official environment repository documentation and the application.yaml configuration shown in the issue. Verify how the gcp-secret-manager backend is configured alongside the git backend, including the application-label, profile-label, token-mandatory, and order settings. Document a working Cloud Run example and confirm that /app1/dev returns data from both backends.