'tfx extension publish' not using cached PAT
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- authentication, cli
Research direction
Start by reproducing the flow with tfx login, then tfx extension publish, and inspect the cached PAT under C:\users\myusername\.tfx\. Trace how authentication is selected for both commands; done means publishing reuses the cached PAT or clearly handles the documented authentication behavior.
Written by the indexing model from the issue text.
Description
I run tfx login and log in successfully. I can check C:\users\myusername\.tfx\ and see the PAT cached there.
I then run tfx extension publish and it prompts me for my PAT. Why isn't it using the cached PAT as I would expect?
- Dominant language
- TypeScript
- Stars
- 386
- Forks
- 142
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 5
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/tfs-cli
-
Area: tfx-cli triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Area: tfx-cli triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Area: tfx-cli DevOps enhancement
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Area: tfx-cli triage
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
Area: tfx-cli triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in microsoft/tfs-cli
Similar issues
-
enhancement providers-api ui-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
homarr-labs/homarr#6976 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day