-
Notifications
You must be signed in to change notification settings - Fork 705
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
Remove assetsvc #4880
Remove assetsvc #4880
Conversation
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
✅ Deploy Preview for kubeapps-dev canceled.
|
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
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.
!!!! Woohoo. Thanks for taking care of moving the pg utils work for now.
Thanks! Now Kubeapps feels ligther 😃 |
The current CI issue seems to be a problem when upgrading from a chart that is passing an old flag.
|
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
// TODO(agamez): remove this after the v2.4.6 release | ||
var assetsvcurlDeprecated string | ||
|
||
func setFlags(c *cobra.Command) { | ||
c.Flags().StringVar(&serveOpts.AssetsvcURL, "assetsvc-url", "https://kubeapps-internal-assetsvc:8080", "URL to the internal assetsvc") | ||
// TODO(agamez): remove 'assetsvc-url' after the v2.4.6 release | ||
c.Flags().StringVar(&assetsvcurlDeprecated, "assetsvc-url", "", "(DEPRECATED)") |
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.
This is an ugly workaround to get the upgrade test passing... otherwise (see my previous comment), they're gonna fail in both our CI and Bitnami's.
Once we release v2.4.6, we can safely delete it
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.
I think it is fine as long as we don't forget to remove it in a later stage.
Thanks!
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.
I'm adding a card to our project dashboard... I can't rely on my memory 👴
* Fix "redundant type from array" warning Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com> * Clean pkg/auth dir Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com> * Clean more pkg/* Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com> * Move pkg/response to kubeops Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com> * Move pkg/http-handler to kubeops Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com> * Move pkg/auth to kubeops Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
Description of the change
This PR finally removes the
assetsvc
code (note that we deprecated it in versionv2.4.0
). This deletion paves the way to tidy up thepkg
folder: there is some logic used by both theassetsvc
and thehelm plugin
; now this logic can be safely moved into thekubeapps-apis
directory. I'll perform those changes in upcoming PRs.Benefits
Less unused code !
Possible drawbacks
N/A (hopefully :P)
Applicable issues
asset-svc
from our codebase + bitnami builds #4847Additional information
will investigate the CI issues tomorrow