-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
UI: chroot namespace listener #23942
Conversation
standby: attr('boolean'), | ||
isActive: equal('standby', false), | ||
clusterName: attr('string'), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clusterName isn't used anywhere, so removed it from the model. The other values are also available on seal-status
which will be available in a chroot scenario, so I moved those below to that section
@@ -44,7 +44,7 @@ export default class VersionService extends Service { | |||
@task | |||
*getVersion() { | |||
if (this.version) return; | |||
const response = yield this.store.adapterFor('cluster').health(); | |||
const response = yield this.store.adapterFor('cluster').sealStatus(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Getting version from this endpoint instead since it's available in non-root namespace.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will probably be updated again to a UI-specific endpoint in the near future, but this will do for now.
ui/app/templates/error.hbs
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the error was happening in the cluster route, we needed to add this highest-level error template to show the error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are subtle bugs introduced when you use {{@model}} instead of {{this.model}} in route templates -- https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/no-model-argument-in-route-templates.md
This route isn't problematic since it doesn't use route params, but in terms of best practices we should make route templates consistently use this.model
Shoutout to @fivetanley for sharing this knowledge (shamelessly stole your language)
? `Vault v${versionName.slice(0, versionName.indexOf('+'))} root` | ||
: `Vault v${versionName}`; | ||
|
||
assert.dom(SELECTORS.cardHeader('Vault version')).hasText(versionText); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated this test because the root namespace badge shouldn't show in community version
Build Results: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have anything to comment on other than great work 👏 . I pulled the branch down and everything looks to be working as expected 🎉
This PR consists of updates to make the UI usable when chroot namespace listener is set.
When accessing the UI via a listener where chroot_namespace is set, but the defined namespace does not exist, the UI will show an error:
Otherwise, the UI should work normally*