Commit 9095c9c
fix: prevent cert provisioning on per-branch testing deploys
Custom domain managed certificates are only meaningful on stable,
long-lived environments (production). Each testing branch gets a unique
ACA FQDN (sharing-test-<slug>.azurecontainerapps.io) that already has
Azure TLS — no custom cert needed.
Setting SHARING_CUSTOM_DOMAIN on the testing GitHub environment caused
every new branch deploy to provision a fresh cert via CNAME validation,
which takes up to 60 minutes and fails if the CNAME points to a different
ACA environment (as it always does for per-branch deploys).
Changes:
- Gate the Reconcile custom domain workflow step on is_prod == 'true'
so it is skipped for all non-main branch deploys even if
SHARING_CUSTOM_DOMAIN is accidentally set on the testing environment
- Add a comment to main.tf explaining the custom_domain var is
production-only
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>1 parent 9f0653e commit 9095c9c
2 files changed
Lines changed: 9 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
175 | 175 | | |
176 | 176 | | |
177 | 177 | | |
178 | | - | |
| 178 | + | |
| 179 | + | |
| 180 | + | |
| 181 | + | |
| 182 | + | |
179 | 183 | | |
180 | 184 | | |
181 | 185 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
191 | 191 | | |
192 | 192 | | |
193 | 193 | | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
194 | 198 | | |
195 | 199 | | |
196 | 200 | | |
| |||
0 commit comments