Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create route - owned domains not proposed #3685

Closed
7 tasks
poblin-orange opened this issue Jul 2, 2019 · 1 comment · Fixed by #3695
Closed
7 tasks

create route - owned domains not proposed #3685

poblin-orange opened this issue Jul 2, 2019 · 1 comment · Fixed by #3695
Labels
bug community Community Raised Issue

Comments

@poblin-orange
Copy link

stratos 2.4.0

Frontend Deployment type

  • [ X] Cloud Foundry Application (cf push)
  • Kubernetes, using a helm chart
  • Docker, single container deploying all components
  • npm run start
  • Other (please specify below)

Backend (Jet Stream) Deployment type

  • [ X] Cloud Foundry Application (cf push)
  • Kubernetes, using a helm chart
  • Docker, single container deploying all components
  • Other (please specify below)

Expected behaviour

I expect all the possible domains to be proposed when creating/mapping a route.

Actual behaviour

The http owned domains of the org are not proposed in the dropbox

Steps to reproduce the behavior

Log output covering before error and any error statements

Insert log hereCopy

Detailed Description

Context

Possible Implementation

@richard-cox
Copy link
Contributor

It looks like we use the shared_domains endpoint instead of domains to populate the drop down, I don't think this includes those owned by an organisation. Not sure why historically this is the case, needs some investigating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug community Community Raised Issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants