microsoft / microsoft/powerplatform-vscode
pac auth create should check if environment exists
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 60
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 14
Description
I wasted 2 hours yesterday to troubleshoot why pac solution sync was throwing an auth profile not found error. I finally figured out the environment url that I was using was incorrect. The environment name was env1, so I thought that the URL is env1.crm6.dynamics.com, but it was actually env1-dev.crm6.dynamics.com. I tried to repro this and I am able to run pac auth create for any environment. pac auth create has to fail with message if the environment URL is invalid. Saying that the authentication was successful is misleading and incorrect.
Contributor guide
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.
Research direction
Start by reproducing the issue with pac auth create using an incorrect environment URL, then trace the authentication command's validation and success reporting. Done means an invalid environment URL causes authentication to fail with a clear message instead of reporting success.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100