VCS provider setup

[erick-prosimo]

I am trying to add a VCS provider, and when looking at the call being made through the UI I am getting a 403. I have validated I am an admin as I can authenticate, create workspaces, etc. Currently when I go to add a VCS provider it just does nothing once I click "connect and continue"

{errors: [{detail: "CreatePermission Denied"}]}
errors
:
[{detail: "CreatePermission Denied"}]
0
:
{detail: "CreatePermission Denied"}
detail
:
"CreatePermission Denied"

[alfespa17]

The terrakube admin group can just create organizations and handle team access.

If you want to work inside any organization adding/updating workspaces, modules, vcs connections or templates you will have to add the "team" inside the organization setting and grant the require permissions.

For example:

In your case you will have to add the "AD Group name" when you create the team.

[erick-prosimo]

Just tried again and still seeing the bad URL "terrakube-callback" being generated. That is not in my env-config. All my values are the correct terrakube-api/reg/ui

[alfespa17]

What is the version of the UI that you are using in the helm chart? Are you using the 2.10.0?

## UI Properties
ui:
  enabled: true
  version: "2.10.0"
  replicaCount: "1"
  serviceType: "ClusterIP"

Could you check this guide? https://docs.terrakube.org/user-guide/vcs-providers/github.com

[erick-prosimo]

Yes, 2.10.0 for everything. I follow that guide and that URL is generated. I have no control over the URL that is generated by Terrakube....

[alfespa17]

This is a bug, I found the issue in the UI code.

https://github.com/AzBuilder/terrakube/blob/main/ui/src/domain/Settings/VCS.jsx#L85

const getCallBackUrl = (id) => {
    return `${window._env_.REACT_APP_TERRAKUBE_API_URL.replace("api","callback")}vcs/${id}`;
  }

I will have to update the logic of the callback URL logic, I never had this issue when I was testing in Gitpod because the API url never have the word "api" in the hostname.

[alfespa17]

I have created a new version that fixes the issue with the callback URL just update to version 2.10.1 running a helm upgrade.