DefangLabs / DefangLabs/docs-chatbot
Revert compose.yaml Azure probe start_period workaround once pulumi-defang releases past PR 536
@defangdevs is already working on this.
Since Sep 7, 2026.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 14h 50m
- Merged PRs (30d)
- 21
Description
PR #134 works around an Azure Container Apps limit: a probe's InitialDelaySeconds is capped at 60, and Defang maps compose's start_period onto it. compose.yaml's app healthcheck was start_period: 240s, so the deploy failed outright. Fix in that PR: start_period: 60s / retries: 10.
pulumi-defang PR 536 (merged 2026-09-05) fixes the clamp at the provider level, so this compose.yaml workaround becomes unnecessary once a release past that merge ships. As of now the latest release is v2.6.0 (2026-08-16), before 536 — releases are blocked on #414 (auto-tag workflow, needs RELEASE_PAT).
Action once a release including PR 536 ships: restore compose.yaml's app healthcheck to retries: 5 / start_period: 240s (or whatever value fits) and drop the explanatory comment.
Filed per review discussion on #134: https://github.com/DefangLabs/docs-chatbot/pull/134#discussion_r3952743001
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.