cloudfoundry / cloudfoundry/stratos
Create and map new route: private domains not available
Open
Nobody has claimed this yet.
community
v3 api
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
Stratos Version
4.0.1
Frontend Deployment type
- [x ] Cloud Foundry Application (cf push)
Backend (Jet Stream) Deployment type
- Cloud Foundry Application (cf push)
Expected behaviour
A private domain can be used for "Create and map new route"
Actual behaviour
A private domain is not available from the ui so that i can't choose the private domain for mapping the route
Steps to reproduce the behavior
Share a private domain with an organization.
Then try to create and map a route using the private domain.
Log output covering before error and any error statements
no logs available
Contributor guide
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 by reproducing the issue in the Stratos UI after sharing a private domain with an organization, then trace the Create and map new route flow. Done means the private domain appears as an available choice and can be used to map the route successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- cloud, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100