Description of problem:

Using Custom Gitlab with customs https port (not default 443) brake the application scaffolding flow when using GitLab as gitops:

When port is added to host in auth, catalog and integrations authentication works but RBAC import of users and groups from GitLab instance brakes:

See this issue supporting port problem:

https://issues.redhat.com/browse/RHTAP-5995

When that got fix we got an issue while creating argo CD resource see details and fix here:

https://issues.redhat.com/browse/RHTAP-5996

After that got fix now we have an issue under the Register Source step. We are not sure how to fix. See details in this Slack thread:

https://redhat-internal.slack.com/archives/C05HGAR2DT5/p1761660039695509

Prerequisites (if any, like setup, operators/versions):

We are using TSSC installer 1.7 with DH 1.7 on a OCP cluster 4.19

Steps to Reproduce

 Install tssc 1.7. Make sure you add the gitlab integration instead of the github one. https://docs.redhat.com/en/documentation/red_hat_advanced_developer_suite_-_software_supply_chain/1.7/html-single/installing_red_hat_advanced_developer_suite_-_software_supply_chain/index#integrating-gitlab_default

Actual results:

We get gitops and source code repos to created in GItlab instance, but not there registrations

Expected results:

We are expecting gitops and source code repos to be created in GItlab instance along with all the required registration.

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

Additional info (Such as Logs, Screenshots, etc):