spring-cloud / spring-cloud/spring-cloud-bus

Spring config server not receiving updated value from application.yml

Open
#260 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

waiting-for-triage
Dominant language
Java
Stars
445
Forks
246
Avg merge
16h 25m
Merged PRs (30d)
5

Description

Hello team,

I have a config server and a config client running locally. I am trying to test updating a config file and having the client get the updates without having to restart. Using spring cloud bus with rabbitmq to do so.

Using a local git repository here, so not able to have a webhook invoke the config server. In place of it I am trying to simulate the call to /monitor endpoint via postman. My config server always says the following in the log

o.s.c.c.monitor.PropertyPathEndpoint : Refresh for: *
2022-04-26 15:58:37.660 INFO 71202 --- [nio-8888-exec-5] o.s.cloud.bus.event.RefreshListener : Received remote refresh request.
2022-04-26 15:58:37.905 INFO 71202 --- [nio-8888-exec-5] o.s.cloud.bus.event.RefreshListener : Keys refreshed []

My postman request looks like this

http://localhost:8888/monitor
{ "path": "*" }

Is there anyways by which I can mimic what a github webhook would do?

It works perfectly fine, meaning updates the changed value on client if I invoke client endpoint using http://localhost:8080/actuator/refresh

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with the /monitor endpoint handling and compare it with the client /actuator/refresh flow, using the posted logs as the baseline. Reproduce the scenario with the local Git repository and Postman request; done means a changed application.yml value reaches the client without a restart.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, java, postman, rabbitmq, spring-boot
Domain
api, backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.