recently went through an exercise where we shifted the git provider from saas gitlab to self hosted gitlab. transition to self hosted gitlab went fine, but afterward, the gitops catalog and the cluster management functionalities were still bound to the original git provider.
we need to provide the end user with an opportunity to change their git server, repo, and personal access token.
recently went through an exercise where we shifted the git provider from saas gitlab to self hosted gitlab. transition to self hosted gitlab went fine, but afterward, the gitops catalog and the cluster management functionalities were still bound to the original git provider.
we need to provide the end user with an opportunity to change their git server, repo, and personal access token.