-
Notifications
You must be signed in to change notification settings - Fork 706
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
Third and final step of package repos API - Package Repository API for Helm #4807
Conversation
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
…-extra Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
…ations Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
@@ -26,7 +26,7 @@ type AppRepositorySpec struct { | |||
Type string `json:"type"` | |||
URL string `json:"url"` | |||
Auth AppRepositoryAuth `json:"auth,omitempty"` | |||
ResyncRequests uint `json:"resyncRequests"` | |||
ResyncRequests int `json:"resyncRequests"` |
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.
Mentioned changed to the type of the existing CRD's ResyncRequests
.
log.V(4).Infof("+helm upgrade repo %s customDetails [%v]", repoRef.Identifier, customDetails) | ||
} | ||
|
||
helmRepo := &HelmRepository{ |
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.
Using this custom HelmRepository
to avoid having 8 parameters in functions signatures :)
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.
Haven't tested it IRL, but looking forward to it while I'm implementing the corresponding changes in the UI.
Signed-off-by: Rafa Castelblanque <rcastelblanq@vmware.com>
✅ Deploy Preview for kubeapps-dev canceled.
|
Description of the change
Third and final step on top of the second PR #4796.
This adds the following implementations and tests:
I had to change the original
AppRepository
CR definition for the fieldResyncRequests
from typeuint
toint
.Benefits
Package repository API is available for direct Helm plugin.
Possible drawbacks
I haven't seen any, but there might be misalignments in the
AppRepository
CRDs data if both the old and this new API are used together over the same CRD. Due to the management of secrets, etc.However, this scenario could only happen during the transition time and should not happen in normal usage at all.
Applicable issues
Additional information
The reason for changing the data type in the original CRD was due to the k8s machinery
DeepCopyJSONValue
being unable to handleuint
(see here).