Closed ardeshir closed 3 weeks ago
Hi @ardeshir, sorry to see that you're having issues.
In your local repository where you're running azd pipeline config --provider azdo
, can you also run git remote get-url --all origin
and provide the results?
The output should look like:
git@ssh.dev.azure.com:v3/<project collection>/<project>/<repo>
for example.
$ git remote get-url --all origin git@ssh.dev.azure.com:v3/fsdi/TechOps/CDS-Azure-Search-OpenAi
@ardeshir Thanks for that. I had looked at the code briefly, but couldn't find the immediate coding error when I confused myself. I can now confirm that it is indeed a bug that affects SSH URIs.
I hope you're not blocked by this. If you are, the quickest workaround is probably to switch to HTTPS when cloning the repository.
@vhvb1989 I was able to get a minimal repro for the panic by commenting out lines 195 and 197 below (to trigger the parsing of project name and repository name into IDs), then rerunning the tests in azdo_provider_test.go
.
I think we need to adjust the parsing logic for handling SSH URIs.
ssh doesn't work on azd for azdo. All the connection is done with a PAT.
You can remove your local origin
remote (git remote remove origin) and then run azd pipeline config
to set the origin again. azd will ask you if you want to create a new repo or use existing. But azd will use a PAT and not ssh.
Another option is you run azd pipeline config --provider azdo --remote-name foo
. This will ignore your origin
remote and will set up a new foo
remote for you
Thanks Wei & Victor,
I am not blocked, I was able to manually create az azdo pipeline, and work on deploying the infra appropriately with CI/CD. But I wanted to pass along the information/stack trace in case it was helpful to others and this project.
This new tool (azd) is a game changer, for devs with some infra control &/or knowledge. Thank you for all the work you’re doing.
Looking forward to this projects growth and success in the future. I am definitely impressed, and will do my best to contribute.
cheers
On Fri, Apr 7, 2023 at 7:03 PM Victor Vazquez @.***> wrote:
ssh doesn't work on azd for azdo. All the connection is done with a PAT.
You can remove your local origin remote (git remote remove origin) and then run azd pipeline config to set the origin again. azd will ask you if you want to create a new repo or use existing. But azd will use a PAT and not ssh.
Another option is you run azd pipeline config --provider azdo --remote-name foo . This will ignore your origin remote and will set up a new foo remote for you
— Reply to this email directly, view it on GitHub https://github.com/Azure/azure-dev/issues/1896#issuecomment-1500732288, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAQCDQ63OBUB7KUNDZLXVTXACTOTANCNFSM6AAAAAAWVZ266M . You are receiving this because you were mentioned.Message ID: @.***>
-- ardeshir.io @. github.com/ardeshir @.
Output from
azd version
azd version 0.7.0-beta.1 (commit 9ce71659f7688d0dc3dda8b84e5accedca58cf01)Describe the bug Command: azd pipeline config --provider azdo
To Reproduce Command: azd pipeline config --provider azdo
Expected behavior Expected to have ado pipeline for template
Environment Information on your environment:
Additional context The repository is a Microsoft Demo [https://github.com/Azure-Samples/azure-search-openai-demo/ ]