Skip to content

Customize Target Proxy URL#4072

Draft
scbedd wants to merge 4 commits intoAzure:mainfrom
scbedd:manually-target-proxy
Draft

Customize Target Proxy URL#4072
scbedd wants to merge 4 commits intoAzure:mainfrom
scbedd:manually-target-proxy

Conversation

@scbedd
Copy link
Copy Markdown
Member

@scbedd scbedd commented Mar 31, 2026

@LarryOsterman here is an example.

@heaths I made a change in existing() to honor an optional value. That might get me yelled at but we'll see 😆

@scbedd scbedd self-assigned this Mar 31, 2026
@github-actions github-actions bot added the Azure.Core The azure_core crate label Mar 31, 2026
Copy link
Copy Markdown
Member

@heaths heaths left a comment

Choose a reason for hiding this comment

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

Yeah, this could work. I was debating on whether we should take an Option<&str> or something instead of reading env vars here, but we read env vars above for Kestrel.

I still wonder if we want to take this, though, instead of figuring out how/why the port is already in use. If we (almost definitely) rightly assume no other agents are running on those machines, when we fail to bind should we actually query and report on what's running off port 5000? This feels more like papering over the problem than trying to understand the root cause and fix it. Then again, maybe it's rare enough it's not worth the investigative effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Azure.Core The azure_core crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants