-
Notifications
You must be signed in to change notification settings - Fork 100
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
Evaluate MaintenancePreconditionsSatisfied constraint #918
Conversation
Should we disable the action or instead show a warning? |
Only show the warning |
@rfranzke does Gardener still trigger the automatic maintenance in case the precondition is not satisfied? |
According to gardener/gardener#3122 (comment) it seems that maintenance is performed anyway, so we need to think of a way to show this information more prominent, not only on the dialogs. |
… and hibernation constraint issues
--> | ||
|
||
<template> | ||
<div v-if="!isMaintenancePreconditionSatisfied" :class="{ 'd-flex' : icon }"> |
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.
The v-if="!isMaintenancePreconditionSatisfied"
should be outside of the component. If the visibility of the component is controlled via a property it should follow the pattern of the toggleable
mixin.
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.
Do we really need the flexbox
container in case of an icon?
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.
flex box does vertical align the icon so that it matches the layout of other icons / texts in the same line
--> | ||
|
||
<template> | ||
<div v-if="!isHibernationPossible && hasHibernationSchedules" :class="{ 'd-flex' : icon }"> |
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.
The v-if="!isHibernationPossible && hasHibernationSchedules"
should be outside of the component. If the visibility of the component is controlled via a property it should follow the pattern of the toggleable
mixin.
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.
Do we really need the flexbox
container in case of an icon?
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.
done
|
||
<script> | ||
export default { | ||
name: 'maintenanceConstraintWarning', |
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.
name: 'maintenanceConstraintWarning', | |
name: 'MaintenanceConstraintWarning', |
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.
Component Names are kebab-case
or PascalCase
https://vuejs.org/v2/guide/components-registration.html#Name-Casing
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 will fix this with a separate PR for all cases where we use camel case instead of kebab case
|
||
<script> | ||
export default { | ||
name: 'hibernationConstraintWarning', |
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.
name: 'hibernationConstraintWarning', | |
name: 'HibernationConstraintWarning', |
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.
Component Names are kebab-case
or PascalCase
https://vuejs.org/v2/guide/components-registration.html#Name-Casing
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 will fix this with a separate PR for all cases where we use camel case instead of kebab case
value: { | ||
type: Boolean | ||
}, | ||
constraintType: { |
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.
The name of the component ist ConstraintWarning
. Why do we repeat the word constraint
but warning
in the property names. I would use type
and message
. Or better use a default slot for the message.
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.
/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.
/lgtm
# Conflicts: # frontend/src/components/ShootListRow.vue
What this PR does / why we need it:
We now show warnings for the Maintenance and Hibernation Constraint Checks.
Which issue(s) this PR fixes:
Fixes #893
Special notes for your reviewer:
Release note: