DefangLabs / DefangLabs/defang
Conflicts when 2+ devs deploy same project to single BYOC account
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 166
- Forks
- 24
- Avg merge
- 10h 8m
- Merged PRs (30d)
- 33
Description
Each project shares the Pulumi state file ("project-name" project, "beta" stack) and each deployment ends up with a provisioned (delegate) domain project-name.USER.defang.app, but the stack only tracks one zone, so when the 2nd dev deploys the project there's a diff: the previous zone (1st dev name) is deleted and a new zone (2nd dev name) is created.
- aws:route53:Record validation-*.nextjs.jordanstephens.defang.app deleted (46s)
- aws:route53:Record alias-*.nextjs.jordanstephens.defang.app deleting (0s)
- aws:acm:Certificate *.nextjs.jordanstephens.defang.app deleting (0s)[retain]
- aws:route53:Zone nextjs.lionello.defang.app deleting (0s)
- aws:route53:Record alias-nextjs.jordanstephens.defang.app deleting (0s)
- aws:acm:Certificate *.nextjs.jordanstephens.defang.app deleted (1s)[retain]
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
No files or tests are named in the issue. Start by reproducing two deployments sharing the Pulumi state file and inspect the Route53 zone changes; done means the second deployment no longer deletes the first developer's zone and records.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100