Skip to content

Conversation

@danegsta
Copy link
Member

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.

Copilot AI review requested due to automatic review settings October 23, 2025 18:58
@github-actions
Copy link
Contributor

github-actions bot commented Oct 23, 2025

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 12323

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 12323"

Copy link
Contributor

Copilot AI left a 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 ILogger parameter to certificate configuration methods to enable resource-specific logging

@danegsta danegsta enabled auto-merge (squash) October 23, 2025 19:18
@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@danegsta danegsta merged commit dc9830d into dotnet:main Oct 24, 2025
303 of 307 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the 13.0 milestone Oct 24, 2025
radical pushed a commit that referenced this pull request Oct 29, 2025
* Cleanup logging when we don't apply certs

* Respond to PR comments
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.

2 participants