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

Don't let users accidentally and permanently dismiss router hostname message #2194

Merged

Conversation

spadgett
Copy link
Member

Knowing the router hostname is vital for setting up a CNAME for routes
with custom hosts. Remove the "Don't Show Me Again" link to prevent
users from accidentally dismissing the message without being able to get
it back.

See #1194 (comment)

@Download FYI, we're also looking at the other feedback you've given.

…message

Knowing the router hostname is vital for setting up a CNAME for routes
with custom hosts. Remove the "Don't Show Me Again" link to prevent
users from accidentally dismissing the message without being able to get
it back.
@spadgett
Copy link
Member Author

[merge]

@openshift-bot
Copy link

Evaluated for origin web console merge up to bac657d

@openshift-bot
Copy link

openshift-bot commented Sep 29, 2017

Origin Web Console Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin_web_console/296/) (Base Commit: 002a70f) (PR Branch Commit: bac657d)

@openshift-bot openshift-bot merged commit 8498bca into openshift:master Sep 29, 2017
@Download
Copy link

Download commented Sep 29, 2017

Wow @spadgett you are on top of it! Much appreciated!

EDIT: I don't think I dismissed it by the way. I'm pretty sure it was never there in the first place. If you look at my screenshot you'll see that the route was created '3 minutes ago'. I specifically created that application to test whether the message was appearing. It did not.

Note that I'm working on Openshift Online v3. I'm not sure whether they customized the web console in some way or are on an older version maybe.

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

Successfully merging this pull request may close these issues.

None yet

4 participants