-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
Continue to add support for git urls as dependency repositories #9482
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please implement the Getter
interface for the git://
protocol? This will allow it to be used for helm install
as well.
Here is an example PR for how this was done for oci://
: #8843
ok, I will do this work as soon as I can. Thanks for your reply. @jdolitsky |
Hi @yxxhero , is there anything i can help you with? And one more question: is it also possible to give a
|
I'm busy recently. I'll try to finish it Thanks very much. |
@jdolitsky ping |
@technosophos @mattfarina @bacongobbler @jdolitsky Look forward to your reply. Thanks very much. |
Hey @yxxhero great work! From the inline docs i get that it is not possible to use subdirectories (contextdir) with this Git functionality:
Is this a design choice? Or is it functionality what is possible to add? For example we (my team) have more files and directories in our helm-chart-repo's. Files needed for CICD pipelines for example. So our repo would be:
So when referencing the helm chart in the dependencies we would like to reference the subdir |
The current design is like this. Of course you can change it and work together to do it. @BlueCog |
I'm going to add contextDir features in my own repo. If it is done. You can test it. Thanks very much. @BlueCog |
@bacongobbler @jdolitsky Does this feature require design documentation? Thanks very much. |
FYI: i've build a Helm client with your PR and tested the functionality (private and public repo's). It works without any issue. Greets |
@jdolitsky ping |
I built the last commit from this PR and am getting the following error when trying to
Another issue I'm getting is, if the name of the dependency doesn't match the name of the repo, I get this error: dependencies:
- name: library
version: 1.2.3
repository: git://git@bitbucket.org:example/helm-library.git
In this case, the name of the chart is |
dependencies:
- name: helm-library
version: 1.2.3
repository: git://git@bitbucket.org:example/helm-library.git |
Great, rebuilt the latest commit (
One question, does the name of the dependency have to match the name of the repo? I've noticed in umbrella/master charts if the name/version of a dependency doesn't match the name/version of the downloaded chart, helm values don't propagate downwards. I'll craft a reproducible example and post it here a little later, maybe this issue is outside of the scope of this PR. Edit: I'll see what I can do regarding the example, I may be mistaken due to having used a build of the old git PR and possible issues in that version. |
@rblaine95 I will find a way to remove this restriction. wait for your example. I will use your example to test it. |
@jdolitsky @technosophos ping |
Any news regarding this PR? |
The PR is already available. I have written HIP and will actively promote the merger of PR. @rblaine95 @BlueCog @pmahoney-raise |
Setting
dependencies:
- name: zenlibs
version: feat/refactor-ingress
repository: git://git@bitbucket.org:zenaptix/helm-zenlibs.git |
@rblaine95 This is the current default behavior. Do you have any idea? |
I thought this PR supports branch names and tags? |
I'll consider your suggestion. @rblaine95 Thanks very much. |
It says here
Edit: if !found {
return nil, fmt.Errorf(`dependency %q is missing git branch or tag: %s.
When using a "git://" type repository, the "version" should be a valid branch or tag name`, d.Name, d.Version)
} pkg/getter/gitgetter.go:L67-69 if version == "" {
return nil, fmt.Errorf("the version must be a valid tag or branch name for the git repo, not nil")
} It looks like your PR already does support branch name, but there's something that checks the version constraint before the git checks which causes it to bomb out. |
@rblaine95 cool, you are right. |
@jdolitsky @technosophos ping |
Signed-off-by: yxxhero <aiopsclub@163.com>
Signed-off-by: Jeff Valore <rally25rs@yahoo.com>
Signed-off-by: yxxhero <aiopsclub@163.com>
Signed-off-by: yxxhero <aiopsclub@163.com>
Signed-off-by: yxxhero <aiopsclub@163.com>
Signed-off-by: yxxhero <aiopsclub@163.com>
Signed-off-by: yxxhero <aiopsclub@163.com>
Signed-off-by: yxxhero <aiopsclub@163.com> add license headers for gitutils Signed-off-by: yxxhero <aiopsclub@163.com>
Signed-off-by: yxxhero <aiopsclub@163.com>
Signed-off-by: yxxhero <aiopsclub@163.com>
In the tendency to GitOps it's sad to see this PR being closed. The maintains don't seem to appreciate the community effort at all. |
@jdolitsky oh. sorry. It's my fault. I will create a PR. Thanks very much. |
Continue the PR #6734 work.
related issue: #9461
If applicable: