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

Fix create app issues related to route visiblility/permissions #1246

Merged
merged 12 commits into from
Sep 12, 2017

Conversation

richard-cox
Copy link
Contributor

  • Ensure we only check for non-empty port/host/path during route exist call
  • Handle failed to create/bind route in create app flow a bit better
    • Better error message
    • Refresh app wall on cancel
  • Optionally show cross in detail-view (to allow wizard to control dismiss params)
  • Show CF api version in cf summary panel

- Ensure we only check for non-empty port/host/path during route exist call
- Handle failed to create/bind route in create app flow a bit better
-- Better error message
-- Refresh app wall on cancel
- Optionally show cross in detail-view (to allow wizard to control dismiss params)
- Show CF api version in cf summary panel
- Looks like this issue was always shown as an error but only intermittently as a failure
- See
  - http://bristol-ui-concourse.ngrok.io/builds/300 (error)
  - http://bristol-ui-concourse.ngrok.io/builds/307 (error and failure)
- "Application View Summary Tab Route Management Application route should show up on CF Endpoints view should allow the route to be un-mapped and then deleted
  - Failed: unknown error: Element is not clickable at point (1276, 663)"
- Couldn't reproduce over several runs locally with both cf's in provo
Copy link
Contributor

@nwmac nwmac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nwmac nwmac merged commit dfead2b into master Sep 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants