-
Notifications
You must be signed in to change notification settings - Fork 91
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
[BUG] - Nebari init fails when using a GitLab repo for the GitOps approach #2268
Comments
Gitlab support has not been tested for some time, so I am not sure if the CI integration would work as well. Would you mind testing that as well, if possible? |
@viniciusdc Yes, I also think there are a couple of stuff we're doing for github that we're not doing for gitlab (e.g., setting up the repo). I think that is beyond the scope of this issue but I'll open another one to work on in future releases. |
Turns out we'll need to account for gitlab groups and subgroups, having repos with the following URL structure:
|
@marcelovilla @kcpevey I was going to suggest that we only fix the CI part of this, as it should depend on the repo when pushing/pulling any changes. But, I think the overall work of getting this running would be enough to actually just implement the whole thing for gitlab itself (with auto provision and CI support) What are your thoughts on this? |
@viniciusdc what do you mean by this? Do you mean Nebari's CI or do you mean rendering the workflow files for the GitOps approach? If it's the latter, those are already being rendered (I haven't tested whether they work, though). @kcpevey and I outlined two approaches to solve this:
I think the second approach is more consistent with what we already have for GitHub. |
Describe the bug
When running
nebari init
and specifying a GitLab repo, the command fails with the following error:Expected behavior
I expect
nebari init
to work properly and create the configuration file according to the options I selected.OS and architecture in which you are running Nebari
Linux ip-172-31-3-104 6.2.0-1017-aws #17~22.04.1-Ubuntu SMP Fri Nov 17 21:07:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
How to Reproduce the problem?
Go over the
nebari init --guided-init
and in the GitOps section try the following:Command output
No response
Versions and dependencies used.
nebari==2024.1.1
Compute environment
None
Integrations
No response
Anything else?
@kalpanachinnappan originally found about this issue
The text was updated successfully, but these errors were encountered: