Repository navigation
add health monitoring - #600
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9c0251fb0e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| .AddEnvironmentVariables().AddInMemoryCollection(new Dictionary<string, string?> | ||
| { | ||
| ["HealthMonitoring:Service:Version"] = Assembly.GetEntryAssembly()?.GetName().Version?.ToString() ?? "0.0.0.0" | ||
| }); |
There was a problem hiding this comment.
For every Docker deployment, this reports the SDK default assembly version (1.0.0.0) rather than the released service version: the Docker build commands in the release/master workflows pass no MSBuild version and neither the project nor Directory.Build.props defines one. Because this in-memory provider is added after environment variables, operators also cannot correct the value with HealthMonitoring__Service__Version; either inject the release version into the Docker build or let deployment configuration override this fallback.
Useful? React with 👍 / 👎.
No description provided.