Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow specifying a custom GitLab URL for non-hosted instances #66

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nextrevision
Copy link

@nextrevision nextrevision commented Sep 26, 2023

Description

Creates a config item in the auth page to allow for a user to specify a private GitLab instance.

config

link

Checklist

Please ensure that each of these items has been addressed:

  • I have tested these changes in my local environment
  • I have added/modified tests as applicable to cover these changes
  • (Atlassian contributors only) I have removed any Atlassian-internal changes including internal modules, references to internal tickets, and internal wiki links

Closes #8

@nextrevision nextrevision requested a review from a team as a code owner September 26, 2023 03:40
@atlassian-cla-bot
Copy link

atlassian-cla-bot bot commented Sep 26, 2023

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution.
If your email is listed below, please ensure that you sign the CLA with the same email address.

The following users still need to sign our CLA:
nado@sagesure.com

Already signed the CLA? To re-check, try refreshing the page.

@nextrevision
Copy link
Author

One outstanding item is accounting for an internal instance in the manifest.yml. Any pointers on how to handle that?

I was tempted to add a storage lookup of the GitLab URL variable in the GitLab client, but followed convention of the group token by passing the variable around. I'm open to doing this differently if you have any suggestions.

@seajoshc
Copy link
Collaborator

Hey @nextrevision, I'm Josh, a product manager on Compass, nice to meet ya 👋 Wow thanks a ton for raising this PR! 🙇‍♂️ Someone from the team will jump in here soon to help out but I wanted to at least acknowledge the PR.

@erica-zhong
Copy link

Hey there @nextrevision ! I’m an engineer on Compass reviewing this PR and I first want to say that this is an amazing contribution! Thanks a lot for all your hard work in making these changes. Self-managed instance support for Gitlab would be a great improvement and we are very interested in making this a reality for customers.

As you mentioned, there is an outstanding item with accounting for an internal instance in the manifest.yml. One way to address this would be to allowlist all external domains with a wildcard matcher https://developer.atlassian.com/platform/forge/manifest-reference/permissions/#valid-domain-formats. However, there may be security concerns about this from customers, so we are currently exploring additional ways to maintain a Compass Gitlab app that is compatible with self-managed instances.

If you would like to get started with your self-managed Gitlab instance and you haven’t already done so, I would suggest forking this repository with your changes and using the app that you have created for now.
Appreciate your patience on this, and thanks again for your contributions!

@nvanheuverzwijn
Copy link

@erica-zhong Hey Erica, any news regarding this feature ? I just discovered compass and was eager to try it but I realized that it didn't support self-hosted (misread the documentation :( ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Idea: Allow custom URL paths for Self Hosted
4 participants