The changes are now pushed to upstream manageiq-ui-classic/manageiq-providers-vmware repos.

manageiq-ui-classic:

commit af927276b8ba38219a1a63d0a470f11df572985f
Author: Jason Frey <jfrey@redhat.com>
Date:   Thu Jan 18 15:42:31 2018 -0500

    Merge branch 'fine-vmrc-warning' into '5.8.z'
    
    Add a warning for VMRC credentials when adding/editing a provider
    
    See merge request !5
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1536537


manageiq-providers-vmware:

commit 0bea4db42965bc21b360f27e7d300932ce3ea03a
Author: Jason Frey <jfrey@redhat.com>
Date:   Thu Jan 18 15:42:25 2018 -0500

    Merge branch 'bz_1507165_disallow_console_if_no_console_credentials_are_defined' into '5.8.z'
    
    Return console unsupported if no console creds
    
    See merge request !1
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1536537

I looked at this on the new release, and the comments in the provider edit screen under the VMRC credentials tab do what is expected.   However when I go to a VM on this provider and try to access a VM Console it puts up a spinner for a moment (usually subsecond) and then returns.   Should we be printing a message saying that the remote console is unsupported, or perhaps just gray out the VM Console button?

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0556