Skip to content

fix: allow negative value for jgit environment to disable refresh#2393

Merged
ryanjbaxter merged 1 commit intospring-cloud:mainfrom
pearsonradu:main
Mar 18, 2024
Merged

fix: allow negative value for jgit environment to disable refresh#2393
ryanjbaxter merged 1 commit intospring-cloud:mainfrom
pearsonradu:main

Conversation

@pearsonradu
Copy link
Contributor

Modify JGitEnvironmentRepository to return false on shouldPull method when refreshRate is a negative value

Fixes gh-2256

Modify `JGitEnvironmentRepository` to return `false` on `shouldPull` method when `refreshRate` is a negative value

Fixes spring-cloudgh-2256
@ryanjbaxter
Copy link
Contributor

Based on your comment in #2394 is this needed or is #2394 the solution to your issue?

@pearsonradu
Copy link
Contributor Author

Both resolve my issue in different ways as long as #2394 works but I need to do some testing. Obeying timeouts would be a better solution for me. Skipping refresh would be a more manual solution since we'd have to update the value when our Git server was restored.

It seems like there is still value in this PR given that an issue was created by other users.

@ryanjbaxter ryanjbaxter merged commit a6aaa43 into spring-cloud:main Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

No open projects
Status: Done

Development

Successfully merging this pull request may close these issues.

Maximum value of spring.cloud.config.server.git.refresh-rate

4 participants

Comments