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
Bug 1840958: Source can be empty in general step #6270
Bug 1840958: Source can be empty in general step #6270
Conversation
|
@yaacov: This pull request references Bugzilla bug 1840958, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
9d55028
to
a96b6dc
Compare
|
@yaacov: This pull request references Bugzilla bug 1840958, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@matthewcarleton please review |
a96b6dc
to
c702494
Compare
| ProvisionSource.URL.toString(), | ||
| ProvisionSource.CONTAINER.toString(), | ||
| ProvisionSource.DISK.toString(), | ||
| ].includes(provisionSourceValue) && getProvisionSourceDiskHelpMsg()} |
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.
can getProvisionSourceDiskHelpMsg be a component rather than a function ?
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.
+1, changed to consts
| onClick={() => goToStep(VMWizardTab.STORAGE)} | ||
| variant={ButtonVariant.link} | ||
| > | ||
| <strong>storage</strong> |
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.
please capitalize
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.
+1
| onClick={() => goToStep(VMWizardTab.NETWORKING)} | ||
| variant={ButtonVariant.link} | ||
| > | ||
| <strong>networking</strong> |
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.
also capitalize here
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.
+1
72af112
to
8910a55
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: irosenzw, yaacov The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
1 similar comment
|
/retest |
|
@yaacov: All pull requests linked via external trackers have merged: openshift/console#6270. Bugzilla bug 1840958 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
@yaacov PTAL
| @@ -110,11 +110,9 @@ const provisioningSourceUpdater = ({ id, prevState, dispatch, getState }: Update | |||
| dispatch( | |||
| vmWizardInternalActions[InternalActionType.UpdateVmSettings](id, { | |||
| [VMSettingsField.CONTAINER_IMAGE]: { | |||
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 fields were kept required so it would be apparent from redux which fields have to be filled.
for this special use case skipValidation was introduced into vm-settings-tab-initial-state.
Please revert this change or give a good reason why it shouldn't be visible in redux and skipValidation should then be removed from initial-state?
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 fields were kept required so it would be apparent from redux which fields have to be filled.
this fields are are not required in the user view, a user can leave them empty and continue filling up the form.
the redux viewer should reflect that.
or give a good reason why it shouldn't be visible in redux and skipValidation should then be removed from initial-state?
This fields are optional, users can fill this information later in the storage tab, we should remove the skipValidation, I can make a folow up PR to fix that.
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.
+1 let's remove the skipValidation then
| @@ -53,6 +62,52 @@ export class VMSettingsTabComponent extends React.Component<VMSettingsTabCompone | |||
| goToStep, | |||
| } = this.props; | |||
|
|
|||
| const provisionSourceValue = this.getFieldValue(VMSettingsField.PROVISION_SOURCE_TYPE); | |||
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 many fields in General Tab and we try to keep this component short as possible. Please either make a new component for this message or make a new component for provision source which will include this functionality.
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.
makes sense to me too 👍
I can make a follow up PR to move the "source" input into a separate component.
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.
+1
URL and Container source are not required in the general step, they are part of the storage step.
Screenshots:

Edit storage "rootdisk" URL source:
Edit storage "rootdisk" Container source:

Edit storage "rootdisk" "any" source:

Edit network "any" net interface
