-
Couldn't load subscription status.
- Fork 713
Cleanup logging when we don't apply certs #12323
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
Conversation
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 12323Or
iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 12323" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR refines the logging behavior for certificate authority trust configuration in DCP executor. The main improvement is moving from unconditional warning logs to conditional, targeted logs that only fire when configuration conflicts are explicitly detected, while also providing the specific environment variable or argument name that caused the conflict.
Key Changes:
- Removed generic warning logs that fired whenever custom certificate configuration was skipped
- Added targeted warning logs that include the specific conflicting argument or environment variable name
- Added
ILoggerparameter to certificate configuration methods to enable resource-specific logging
|
Azure Pipelines successfully started running 2 pipeline(s). |
* Cleanup logging when we don't apply certs * Respond to PR comments
Description
I was over logging when custom certificates weren't being applied. This PR ensures we only log when we're explicitly skipping applying certificates due to conflicting configuration. Additionally, I'm logging the environment variable name or argument flag that caused us to skip the config to make it easier to troubleshoot.