Better context on `domain list`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 84
- Forks
- 26
- Avg merge
- 20h 27m
- Merged PRs (30d)
- 13
Description
What would you like to be added:
A better return from the qovery container domain list command. I use it with the --json flag to be able to list and use different link from that container elsewhere. But at the moment it is just returning a link, with absolutly no id and no context. A return indicating the link between port from the container and the link would be amazing. I can make some grep / sed to get the link but It's clearly not a viable idea and can break easily.
Why is this needed:
More ease and less tinkering on my end, really just a QOL functionality.
Edit:
I have tried with the --verbose flag, and the return from the API seems to be more thorough, but seems to be translated when passing a --json flag. But extracting that return is a bit tedious.
Result in the --verbose return
{
"results": [
{
"url": "https://custom+default-url.from.qovery",
"internal_port": 8010,
"external_port": 443,
"is_qovery_domain": true,
"is_default": false
},
{
"url": "https://default-url.from.qovery",
"internal_port": 8020,
"external_port": 443,
"is_qovery_domain": true,
"is_default": true
}
]
}
Instead of
[
{
"domain": "custom+default-url.from.qovery",
"id": null,
"type": "BUILT_IN_DOMAIN",
"validation_domain": null
},
{
"domain": "default-url.from.qovery",
"id": null,
"type": "BUILT_IN_DOMAIN",
"validation_domain": null
}
]
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 the qovery container domain list command and compare how its --json and --verbose outputs are produced. Done means the JSON output preserves the domain URL together with its relevant port and context fields, rather than returning only the domain and null metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100