Azure / Azure/bicep

bicep local-deploy timeout

Open
#17,756 3 comments 0 reactions 0 assignees View on GitHub
Local Deploy
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 2h
Merged PRs (30d)
79

Description

**Bicep version**
Bicep CLI version 0.37.4 (27cc8db2ed)

**Describe the bug**
While deploying a custom extension (Databricks), the resource that I attempt to deploy times out:

serialized:'{
"code": "RpcException",
"target": "/resources/gitRepo",
"message": "Rpc request failed: The request was canceled due to the configured HttpClient.Timeout of 30 seconds elapsing.",
"details": []
}'

**To Reproduce**

Run the following code:

```bicep
// requires Git credentials to be configured in Settings -> Linked Accounts

targetScope = 'local'

param workspaceUrl string

extension databricksExtension with {
workspaceUrl: workspaceUrl
}

resource gitRepo 'Repo' = {
provider: 'GitHub'
url: 'https://github.com/Azure/bicep'
branch: 'main'
}

output repoId string = gitRepo.repoId
```

The repository is eventually made in Azure Databricks, but the local-deploy times out. This is also with other resources.

**Additional context**

> [!NOTE]
> The repository is open at: https://github.com/Gijsreyn/bicep-ext-databricks. I have also tried setting the timeout to 180 without success.

Contributor guide

Open the contributing guide

Research direction

Start by running the supplied Bicep local-deploy reproduction with the Databricks extension and verify whether the repository is created despite the timeout. Trace the local-deploy request through the Bicep CLI and compare its 30-second HttpClient timeout with the eventual deployment result. Done means the deployment completes without reporting a timeout for this and comparable resources.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.