Epic Goal

• Add validation to the vCenter server field in Credentials form to prevent cluster deployment failures

From BZ:  https://bugzilla.redhat.com/show_bug.cgi?id=2032000 

Why is this important?

• The vCenter server field is required to be a raw hostname and not a full URL, entering in a full URL will result in in cluster provision failures

Scenarios

1. In Create credential flow for vSphere, on the VMware step, add validation to the vCenter server input field
   1. The validation function should check if the field was entered as a full URL.  If so, throw an error message indicating that the value needs to be a fully qualified hostname.
   2. If an IP address was input, validate that the IP address is in correct format.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• All scenarios complete

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>