DefangLabs / DefangLabs/defang
Load balancer endpoints not shown at the end of a deployment
Open
Nobody has claimed this yet.
byoc
- Dominant language
- Go
- Stars
- 166
- Forks
- 24
- Avg merge
- 10h 8m
- Merged PRs (30d)
- 33
Description
At the moment we show internal DNS and public domain names (using defang.app domain) but we don't show the load balancer endpoint, which is important for a user to have. It's visible with --verbose but it should be available by default.
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
Locate the deployment-completion output and the existing --verbose path that displays the load balancer endpoint. Make the endpoint appear by default alongside the internal DNS and public defang.app names, then verify the normal and verbose deployment output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100