Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

bicep-deploy missing nowait parameter

Open
#188 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, github-actions, typescript
Domain
cloud, devops

Research direction

Start by inspecting the bicep-deploy action's deployment flow and how its inputs are exposed. Define how a nowait option should behave for long-running SQL Managed Instance deployments, then verify that asynchronous deployment avoids GitHub Actions timeouts while preserving the existing synchronous behavior.

Written by the indexing model from the issue text.

Description

Needs-Repro-Info

There doesn't appear to be a way to make the deployment asynchronous. For deployment of SQL Managed Instances, which can take up to 4 hours, this doesn't work. We run into github action timeouits. This will force us to use hybrid runners, or I guess use the azure cli directly to deploy the bicep file.

Can you look into adding a nowait parameter to bvicep-deploy?

Dominant language
TypeScript
Stars
66
Forks
20
Avg merge
16h 13m
Merged PRs (30d)
22

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/bicep-deploy

All issues in Azure/bicep-deploy

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.