DefangLabs / DefangLabs/defang
Renaming service with x-defang-static-files fails
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 166
- Forks
- 24
- Avg merge
- 10h 8m
- Merged PRs (30d)
- 33
Description
2026-03-15T02:16:57.364Z cd ** error: sdk-v2/provider2.go:572: sdk.helper_schema: creating CloudFront Distribution: operation error CloudFront: CreateDistributionWithTags, https response error StatusCode: 409, RequestID: 750b9144-a2a2-4076-9020-a3441436d1da, CNAMEAlreadyExists: One or more of the CNAMEs you provided are already associated with a different resource.: provider=aws@6.83.2
This happens because the "new" CDN is spun up before the old one is deleted, with no apparent link between the two resources.
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.
Research direction
Start at sdk-v2/provider2.go:572 and reproduce the service rename with x-defang-static-files using the AWS provider. Trace how the CloudFront Distribution is created and how the prior resource is removed. Done means the rename no longer fails with CNAMEAlreadyExists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100