-
Notifications
You must be signed in to change notification settings - Fork 14
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
feat : custom repositories #373
base: main
Are you sure you want to change the base?
Conversation
How can I test this? Also, there's some formatting errors in the code - can be fixed by running |
You can run console,api locally and checkout my branch |
30c8894
to
6aa78d8
Compare
Is there a reason why this is only for Civo? These kind of features should be implemented on all clouds to prevent difference in features between them. It's not a great experience for users on other cloud if they can't have the same features, it's more annoying to document, and a pain to maintain after :) |
Now it's on all clouds Fred, sorry for not updating it |
@jokestax great, I didn't check the code yet, just check the PR title :) |
92221ba
to
5076abd
Compare
5076abd
to
b547785
Compare
Co-authored-by: Patrick D'appollonio <[email protected]>
This reverts commit 0173e0782480c854202e58a075b3ea063bf8c331.
… 0.102.0 skip-checks:true
… 0.103.0 skip-checks:true
… 0.104.0 skip-checks:true
… 0.105.0 skip-checks:true
* fix: secret gitops catalog * added fix for import cluster * format type * format-type-typo * revert
* fix: import * Update internal/secrets/import.go Co-authored-by: Patrick D'appollonio <[email protected]> * fix: return --------- Co-authored-by: Patrick D'appollonio <[email protected]>
we can now deploy multiple repos on same organistation using below flags :
"--gitopsRepoName" metaphorRepoName "adminTeamName" "developerTeamName"
but we have to use kubefirst repo branch "feat-custom-repo" and kubefirst-gitops-template repo branch "feat-custom-repo" until its merged into main