Skip to content
This repository has been archived by the owner on Nov 15, 2022. It is now read-only.

Update client go to 3.0.0 #181

Merged
merged 2 commits into from
Jul 26, 2017
Merged

Conversation

surajssd
Copy link
Member

@surajssd surajssd commented Jul 25, 2017

Fixes #81

Copy link
Collaborator

@concaf concaf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, except for one comment left, and was just curious that why were tests failing initially when you sent this PR and what fixed that?

And great work! 🎉

glide.yaml Outdated
- pkg/apis
- package: k8s.io/apimachinery
version: release-1.6
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did we pin the version to "release-1.6"? client-go v3.0.0 does that already, right? Any reason we had to specify that explicitly here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I don't pin it, it's master was being pulled leading it to not compile.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gotcha, can you add that as a comment?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

comment where?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:) In glide.yaml, on the line above - package: k8s.io/apimachinery

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but comments in glide.yml are bit tricky as everytime this file gets modified using glide command comments are lost :-( we must be careful with that

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

haha, same time @kadel :P

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

umm, @kadel glide update will modify glide.lock, not glide.yml, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done, thanks @kadel @containscafeine

Copy link
Member

@kadel kadel Jul 26, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

umm, @kadel glide update will modify glide.lock, not glide.yml, right?

yes, only thing that automatically modifies glide.yaml as far as I know is glide get

@surajssd
Copy link
Member Author

I will wait on @kadel to merge this one, cause this is big one!

Also lock down k8s.io/apimachinery to release-1.6
@surajssd
Copy link
Member Author

@kadel is this good to go in?

@kadel
Copy link
Member

kadel commented Jul 26, 2017

@kadel is this good to go in?

Haven't got time to look at it closely yet 😞

@@ -1,5 +1,5 @@
/*
Copyright 2014 The Kubernetes Authors.
Copyright 2017 The Kedge Authors All rights reserved.
Copy link
Member

@kadel kadel Jul 26, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you rebase with current master?
This diff looks weird. single_container_object.go file shouldn't even exist after #180 being merged

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did somehow it came, but yeah updated and pushed!

@kadel kadel merged commit ec78a58 into kedgeproject:master Jul 26, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants