Is your feature request related to a problem? Please describe. No problem: quite the contrary: Spring Cloud Config Server is so useful I'm trying to extend its reach
Describe the solution you'd like
You can set environment variables for your Github Actions in a static fashion by assigning them to entries in the Github Actions workflow .yaml. There are a ton of values id like to source from my spring Cloud Config Server, instead of having to maintain them in both Github Secrets and in the Spring Cloud Config Server, for use at build-time and app runtime.
Github Actions have a pretty simple mechanism to dynamically contribute (append) environment variables definitions - in the form KEY=VAL\n - to whatever file is described by the environment variable $GITHUB_ENV. So, echo SPRING_PROFILES_ACTIVE=cloud >> $GITHUB_ENV` would set the environment variable for all subsequent stages in the workflow.
So, i wrote a little program (didn't get fancy) to connect to my authenticated S-C-Config Server instance and output them to the $GITHUB_ENV variable. It's a little CLI. That was the easy part. Granted, my implementation was a trivial RestTemplate call. I'm sure I'd have been smarter to use some S-C-Config Client autoconfig, but didn't want to wrestle with GraalVM and S-Cloud-Config on an older version of Boot. Wrapping it in a Github Action so it feels like an actual honest-to-goodness GH Action would be even cooler.
Describe alternatives you've considered See above
Additional context I've also filed an issue to support reading config from Spring Cloud Config Server as a ConfigMap. Generally, Id like S-C-Config Server to be with me at every step of the lifecycle of an app, from immediately after the K8s cluster is configured until the very last request in my apps.