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
mgr/dashboard: Hide maintenance option on expand cluster #46702
mgr/dashboard: Hide maintenance option on expand cluster #46702
Conversation
jenkins retest this please |
<div class="form-group row" | ||
*ngIf="pageURL === 'hosts'"> |
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.
That's ok, but (personally) I think it's preferable that conditions express what's the underlying reason for doing something.
There are multiple ways:
- For example, in the cluster expansion workflow, this component will be child/grandchild of the cluster expansion component, so if you inject that component in the constructor you'll be able to check that condition which really express why this is hidden (
if parentIsClusterCreation then hide this
). - Even better, you can extend the interface of the hosts page with a new argument:
hideMaintenance
ordeploymentStage
, etc...
IMHO all those checks (if parentIsClusterCreation
, if hideMaintenance
, if deploymentStage
) better reflect the intention of this change.
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 agree in this case.
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.
jenkins test make check |
<div class="form-group row" | ||
*ngIf="pageURL === 'hosts'"> |
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 agree in this case.
jekins test dashboard cephadm |
jenkins test make check |
Fixes: https://tracker.ceph.com/issues/56070 Signed-off-by: Nizamudeen A <nia@redhat.com>
a662edd
to
d66bfe0
Compare
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.
works locally so lgtm
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.
changes LGTM.
jenkins test api |
2 similar comments
jenkins test api |
jenkins test api |
Fixes: https://tracker.ceph.com/issues/56070
Signed-off-by: Nizamudeen A nia@redhat.com
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this please
jenkins test classic perf
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test dashboard cephadm
jenkins test api
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox
jenkins test windows