"$ rhoas cluster connect --service-type service-registry": oauthTokenUrl is not correct

[btison]

Description

Version:
0.46.1

When connecting a service registry instance to an OpenShift namespace using rhoas cluster connect, the resulting ServiceRegistryConnection CR uses an incorrect URL for the oauthTokenUrl

Steps to reproduce

• connect a service registry instance to an OpenShift namespace

  $ rhoas cluster connect -n user1-globex --service-type=service-registry --service-name=globex -y
  

• inspect the generated ServiceRegistryConnection CR

Expected vs actual behaviour

Expected: in the ServiceRegistryConnection CR the value of the status.metadata.oauthTokenUrl is set to https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/token

Actual: in the ServiceRegistryConnection CR the value of the status.metadata.oauthTokenUrl is set to https://identity.api.openshift.com/auth/realms/rhoas/protocol/openid-connect/token

Logs

[wtrocki]

What is the rhoas cluster status output.

We require "latest" version of the operator to get mas-sso url removed:

Release https://github.com/redhat-developer/app-services-operator/releases/tag/0.9.7

[btison]

Ok, that's probably the problem. My RHOAS operator is on version 0.9.6, but that seems to be the most recent version available on OpenShift at the moment it seems.

[wtrocki]

Ok. I will need to verify and release it.