🐾 In providers forms, missing explanation for invalid field

[yaacov]

Refs:
docs: https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/2.4/html/installing_and_using_the_migration_toolkit_for_virtualization/index

In
create provider form
edit credentials form

we have field validation errors without explanation of what need to be fixed, each error message need to be evaluated with documentation, backend implementatin and validatation code.
a. check validation is correct for this field
b. check validation text is correct for this field
c. add "how to fix" to the text, for exmple "Invalid domain name." if should be "Invalid OpenStack domain name, spaces are not allowed, check that the domain name does not include spaces."

contact Richard from the doc team for specific text where needed.

Screenshot:

[yaacov]

doc team contact: @RichardHoch

[yaacov]

cc:// @RichardHoch @anarnold97

[yaacov]

changing from bug to feature, to indicate it is not a bug

[yaacov]

@sgratch hi
when fixing the help texts:
a. please note item c in this issue:

c. add "how to fix" to the text, for exmple "Invalid domain name." if should be "Invalid OpenStack domain name, spaces are not allowed, check that the domain name does not include spaces."

b. please follow PF4 suggestion on how to write help texts:

Make your error messages brief yet descriptive. A useful pattern to follow is Description, Reason, and Resolution:

see: https://www.patternfly.org/ux-writing/error-messages for more information

for example, when we describe what is wrong with a "name" input, we should be brief, we should not try to write the complete definition of RFC 1123 but we can say the name should be valid k8s name, ask the user to verify, and if possible give them a link for our or k8s documentation.

for example if the name is invalid (not if it's not uniqe) a posible help text can be:

Invalid name, the name does not follow Kubernetes guidelines, check that it only contains lowercase alphanumeric characters, '-' or '.', Lean more {=> link to docs}.

[yaacov]

Note: in some future we can make the help text specific for the error, for example if an input include space when it should not, we can change the "What happen" and "How to solve" to "the X include space, remove the spaces and try again"

[yaacov]

a. check validation is correct for this field

submitted and merged upstream: #712

[yaacov]

update help message for oVirt URL:
submitted upstream: #732

[yaacov]

update help message for vSphere URL:
submitted upstream: #736

[yaacov]

#756 - fix msg in VDDK input

[yaacov]

🎂 🎈