`azd provision` doesn't honor the flag to `use existing project` and the tool is not getting deployed on provision too.

[mohitpavan]

Problem

Im doing azd ai agent init -m "https://github.com/microsoft-foundry/foundry-samples/blob/main/samples/python/hosted-agents/agent-framework/responses/14-browser-automation-agent/azure.yaml" --deploy-mode container

It asked me if i should use the existing project, and i selected the desired project.

Went to the cd bat... and done azd provision and it asked me the subscriptionId and Location again (which i feel can be coming from the init's flag too if the Use existing project is selected).

Selected the same location and subId, and it created a new project however which is not expected for me.

Idk why is this new project getting created.

And in the new project, the tool is not available.

and even toolbox is getting deployed in azd deploy only.

observations:
azd env is not setting up in the bat folder and is asking to initialise with subId and the location.

[ChenxiJiang333]

Hi @mohitpavan, by using an existing project, you don't have to run azd provision. You can just move on to azd ai agent operations.

[mohitpavan]

@ChenxiJiang333 but why is it not creating the tool at the 1st place ?
I agree on the part of provision creating new project, but the tool is expectted to be created ?

[mohitpavan]

Okay tooool is getting deployed after updating the version to beta6, but I have one more issue:

    browserautomation:
        host: azure.ai.connection
        authType: ${PLAYWRIGHT_AUTH_TYPE}
        category: PlaywrightWorkspace
        credentials:
            key: ${PLAYWRIGHT_SERVICE_ACCESS_TOKEN}
        metadata:
            resourceId: ${PLAYWRIGHT_SERVICE_RESOURCE_ID}
        target: ${PLAYWRIGHT_SERVICE_URL}

I used this and in the pre-prov script we are settiing the Auth_type

.env for reference:

PLAYWRIGHT_AUTH_TYPE="ProjectManagedIdentity"
PLAYWRIGHT_SERVICE_ACCESS_TOKEN="null"
PLAYWRIGHT_SERVICE_RESOURCE_ID="/subscriptions/7c71b563-0dc0-4bc0-bcf6-06f8f0516c7a/resourceGroups/mitsha-rg/providers/Microsoft.LoadTestService/playwrightWorkspaces/mitsha-pww"
PLAYWRIGHT_SERVICE_URL="wss://eastus.api.playwright.microsoft.com/playwrightworkspaces/9838e261-2e5e-43bd-bed2-c48ec130ecca/browsers"
TOOLBOX_BROWSER_AUTOMATION_TOOLS_MCP_ENDPOINT="https://cog-xmqyxghrbwifc.services.ai.azure.com/api/projects/bat-python-maf-dev/toolboxes/browser-automation-tools/versions/3/mcp?api-version=v1"

butt tthe deployment is throwing error saying auth_type is not right.

    "details": [
      {
        "code": "Conflict",
        "message": "{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"DeploymentFailed\",\r\n        \"target\": \"/subscriptions/7c71b563-0dc0-4bc0-bcf6-06f8f0516c7a/resourceGroups/rg-bat-python-maf-dev/providers/Microsoft.Resources/deployments/foundry-resources\",\r\n        \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.\",\r\n        \"details\": [\r\n          {\r\n            \"code\": \"ResourceDeploymentFailure\",\r\n            \"target\": \"/subscriptions/7c71b563-0dc0-4bc0-bcf6-06f8f0516c7a/resourceGroups/rg-bat-python-maf-dev/providers/Microsoft.Resources/deployments/foundry-connections\",\r\n            \"message\": \"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.\",\r\n            \"details\": [\r\n              {\r\n                \"code\": \"DeploymentFailed\",\r\n                \"target\": \"/subscriptions/7c71b563-0dc0-4bc0-bcf6-06f8f0516c7a/resourceGroups/rg-bat-python-maf-dev/providers/Microsoft.Resources/deployments/foundry-connections\",\r\n                \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.\",\r\n                \"details\": [\r\n                  {\r\n                    \"code\": \"UserError\",\r\n                    \"message\": \"Unexpected AuthType in request body: [${PLAYWRIGHT_AUTH_TYPE}]. Supported types: RegistryIdentity,Basic,None,PAT,SAS,ServicePrincipal,AccessKey,ApiKey,CustomKeys,OAuth2,AccountKey,AAD,DelegatedSAS,ProjectManagedIdentity,AccountManagedIdentity,UserEntraToken,AgentUserImpersonation,AgenticIdentityToken,AgenticUser,UserTokenAndProjectManagedIdentity,DeveloperConnection\",\r\n                    \"details\": []\r\n                  }\r\n                ]\r\n              }\r\n            ]\r\n          }\r\n        ]\r\n      }\r\n    ]\r\n  }\r\n}"
      }
    ]

[huimiu]

Works after updating the authType: ${PLAYWRIGHT_AUTH_TYPE} to authType: "ProjectManagedIdentity", we need to take a look the issue with authType resolve logic