Skip to content

[python] noAuth results in optional cred parameter - #9298

Merged
iscai-msft merged 2 commits into
microsoft:mainfrom
iscai-msft:python/optionalCred
Jan 13, 2026
Merged

iscai-msft merged 2 commits into
microsoft:mainfrom
iscai-msft:python/optionalCred

Conversation

@iscai-msft

@iscai-msft iscai-msft commented Jan 6, 2026 •

Copy link
Copy Markdown
Member

@pkg-pr-new

pkg-pr-new Bot commented Jan 6, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/microsoft/typespec/@typespec/http@9298
npm i https://pkg.pr.new/microsoft/typespec/@typespec/http-client@9298

commit: 593f045

@github-actions

github-actions Bot commented Jan 6, 2026

Copy link
Copy Markdown
Contributor

All changed packages have been documented.

  • ✅ @typespec/http-client-python
Show changes

@typespec/http-client-python - fix ✏️

Fix clients with NoAuth credentials to have optional generated credential parameters

@azure-sdk

Copy link
Copy Markdown
Collaborator

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension

@pvaneck Paul Van Eck (pvaneck) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks! Tested with my use case, and the client no longer requires a credential anymore.

@iscai-msft
iscai-msft added this pull request to the merge queue Jan 13, 2026
Merged via the queue into microsoft:main with commit 89ef757 Jan 13, 2026
38 checks passed
@iscai-msft
iscai-msft deleted the python/optionalCred branch January 13, 2026 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

emitter:client:python Issue for the Python client emitter: @typespec/http-client-python

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: NoAuth with OAuth2Auth emits Client that still requires credentials

5 participants