[Issue] azd pipeline config - files with git errors when configuring AzDO

[brandonh-msft]

• Make sure you've installed the latest version using instructions in the wiki

Output from azd version
azd version 1.10.1 (commit 31409a33266fb4a5fdbb644bc83988e725d6c7c9)

Describe the bug
When running azd pipeline config and providing a PAT w/ all the scopes required per the docs, I am met with an error during the git phase:

  (✓) Done: Checking current directory for Git repository

ERROR: ensuring git remote: Looking for repository: Request returned status: 404 Not Found

To Reproduce
My use case has a root-level respository, then a backend/ subfolder where I have run azd init and then customized the deployment and azure.yaml file to work for my setup. Nothing crazy, just adding some settings and using a custom up workflow to deploy containers in a specific order.

Expected behavior
I'm new to azd, so not entirely sure what the output of pipeline config is supposed to be, but... I wouldn't expect errors.

Environment
Information on your environment:

• .NET 8, ASP.NET Core
• VS 17.11
• VSCode 1.93.1

Additional context

Output from `--debug`

  |      =| Initialize bicep provider2024/10/03 16:24:51 main.go:50: Retry: =====> Try=1
2024/10/03 16:24:51 main.go:50: Request: ==> OUTGOING REQUEST (Try=1)
   GET https://graph.microsoft.com/v1.0/me
   Authorization: REDACTED
   User-Agent: azsdk-go-graph/1.0.0 (go1.23.0 X:loopvar; Windows_NT),azdev/1.10.1 (Go go1.23.0 X:loopvar; windows/amd64)
   X-Ms-Correlation-Request-Id: REDACTED

  |       | Initialize bicep provider2024/10/03 16:24:52 main.go:50: Response: ==> REQUEST/RESPONSE (Try=1/113.2799ms, OpTime=113.8287ms) -- RESPONSE RECEIVED
   GET https://graph.microsoft.com/v1.0/me
   Authorization: REDACTED
   User-Agent: azsdk-go-graph/1.0.0 (go1.23.0 X:loopvar; Windows_NT),azdev/1.10.1 (Go go1.23.0 X:loopvar; windows/amd64)
   X-Ms-Correlation-Request-Id: REDACTED
   --------------------------------------------------------------------------------
   RESPONSE Status: 200 OK
   Cache-Control: no-cache
   Client-Request-Id: REDACTED
   Content-Type: application/json;odata.metadata=minimal;odata.streaming=true;IEEE754Compatible=false;charset=utf-8
   Date: Thu, 03 Oct 2024 23:24:51 GMT
   Odata-Version: REDACTED
   Request-Id: 5e877c36-86e5-4dd5-a82b-6ab7df36856f
   Strict-Transport-Security: REDACTED
   Vary: REDACTED
   X-Ms-Ags-Diagnostic: REDACTED
   X-Ms-Resource-Unit: REDACTED

2024/10/03 16:24:52 main.go:50: Retry: response 200
2024/10/03 16:24:52 main.go:50: Retry: exit due to non-retriable status code

Configure your Azure DevOps pipeline

  |       | Checking current directory for Git repository2024/10/03 16:24:52 command_runner.go:307: Run exec: 'git -C D:\azdo\msft\project\backend remote get-url origin' , exit code: 0
-------------------------------------stdout-------------------------------------------
https://org@dev.azure.com/org/project/_git/repo
2024/10/03 16:24:52 command_runner.go:307: Run exec: 'git -C D:\azdo\msft\project\backend branch --show-current' , exit code: 0    
-------------------------------------stdout-------------------------------------------
feature/infra-via-bicep-and-azd
  (✓) Done: Checking current directory for Git repository

ERROR: ensuring git remote: Looking for repository: Request returned status: 404 Not Found

[rajeshkamal5050]

@vhvb1989 can you take a look?

[rajeshkamal5050]

@v-xuto can you help triage this?

[Yionse]

@brandonh-msft, We are unable to reproduce the issue. Please confirm the following related configurations and permissions:

• Execute git remote -v to check if the address of the remote repository is correct.
• Check that the Azure DevOps PAT has full access permissions.

If it still cannot be resolved, please provide more details about your issue, such as: azure.yaml file and azure-dev.yml file, and all output information about executing command azd pipeline config --provide azdo.

[microsoft-github-policy-service]

Hi @@brandonh-msft. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

[microsoft-github-policy-service]

Hi @@brandonh-msft, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.