Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config spec updates, more logging #26

Merged
merged 3 commits into from
Mar 27, 2020
Merged

Config spec updates, more logging #26

merged 3 commits into from
Mar 27, 2020

Conversation

Tratcher
Copy link
Member

Incremental updates to the config spec.

  • New route format from Simplified route config #24
  • Proposal to combine the backend & endpoint structures
  • Config reload investigations, this already works well for routes, endpoints, backends. There are open questions, but Kestrel config is the biggest rock to tackle. I added debug logs to show that the reload was working as expected.

@@ -104,6 +104,15 @@ private void UpdateRuntimeBackends(DynamicConfigRoot config)
currentBackendConfig.HealthCheckOptions.Port != newConfig.HealthCheckOptions.Port ||
currentBackendConfig.HealthCheckOptions.Path != newConfig.HealthCheckOptions.Path)
{
if (currentBackendConfig == null)
{
_logger.LogDebug("Backend {backendId} has been added.", configBackend.BackendId);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to confirm, the {} syntax without the $ is actually using an ASP.NET Core-specific scheme for naming the holes in the format?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, logging will fill that in.

@Tratcher Tratcher merged commit d71dfd0 into master Mar 27, 2020
@Tratcher Tratcher deleted the tratcher/config branch March 27, 2020 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants