-
Notifications
You must be signed in to change notification settings - Fork 173
Conversation
0ab9289
to
9da8fa5
Compare
I think it's worth moving to
|
Signed-off-by: Jessica Yao <[email protected]>
Currently the component APIs are grouped into the same file as manager.go. As more component APIs are added, managers.go will be difficult to maintain. Similar to the environment and registry APIs, component APIs will be moved into a separate file component.go Signed-off-by: Jessica Yuen <[email protected]>
This adds a high level 'component' command and a 'component list' command. 'component list' will pretty print all the components in ksonnet application directory. To accomplish this, an API is added to the metadata manager that returns all components. Components are the individual files in /components, with the path extension trimmed. Signed-off-by: Jessica Yuen <[email protected]>
Signed-off-by: Joe Beda <[email protected]>
Signed-off-by: Joe Beda <[email protected]>
Signed-off-by: bryanl <[email protected]>
9da8fa5
to
37c9398
Compare
@hausdorff those issues haven't presented themselves in this change. Also, we can potentially update |
Signed-off-by: bryanl <[email protected]>
58bda1d
to
71edfc9
Compare
@hausdorff Also, yes this completes the transition to |
@bryanl We should upgrade I'll take a look at the review in a bit. |
@bryanl Oh, also, if we're going to transition to |
The goal was to make the changes in steps. 1) move to dep 2) update client-go and friends. This PR Is only the first step. |
@bryanl ok, so, just to be clear: the plan is to update kubecfg as well, yes? |
Summarizing offline conversations: yes, we're planning on updating kubecfg. |
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.
Is it possible to dep
in one commit, and then upgrade dependencies in another? I'm ok shipping this if we do that one thing.
@hausdorff I'm going to review to see if that is possible. dep and govendor. I may have to go back and adjust each dep by hand. The problem is explicit vs implicit dependencies. |
@bryanl Ok, if it's not easy, then I recommend just shipping it as-is. Another way to ameliorate this risk is to ship a release candidate for 0.9, so that at least people have a chance to test it in the wild. (I bring this up because we have a bunch of version-specific fixes for bugs in our dependencies, strung throughout the code, so. Ick.) |
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'll pre-emptively vote "ship it", since one of those two scenarios will happen, and then it will get shipped either way.
Just incase you miss this, should do a rebase before merging. Some commits are dirty. |
I've noticed this is taking a lot longer to build (even on subsequent builds). Are you seeing similar behavior @bryanl ?
|
I didn't notice. Will investigate in the morning.
…On Wed, Jan 10, 2018 at 6:13 PM Jess ***@***.***> wrote:
I've noticed this is taking a lot longer to build (even on subsequent
builds). Are you seeing similar behavior @bryanl
<https://github.com/bryanl> ?
➜ ksonnet git:(pr-265) ✗ time make
go build -o ks -ldflags="-X main.version=foo " .
./docs/generate/update-generated-docs.sh
make 42.67s user 4.83s system 209% cpu 22.687 total
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#265 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAA8I__nh82cX1aSo0yGpDm7XQuIgJuks5tJUQYgaJpZM4RTUQx>
.
|
on master:
on current:
|
name = "k8s.io/client-go" | ||
packages = ["discovery","discovery/fake","dynamic","kubernetes/scheme","kubernetes/typed/core/v1","pkg/api","pkg/api/install","pkg/api/v1","pkg/apis/apps","pkg/apis/apps/v1beta1","pkg/apis/authentication","pkg/apis/authentication/v1","pkg/apis/authentication/v1beta1","pkg/apis/authorization","pkg/apis/authorization/v1","pkg/apis/authorization/v1beta1","pkg/apis/autoscaling","pkg/apis/autoscaling/v1","pkg/apis/autoscaling/v2alpha1","pkg/apis/batch","pkg/apis/batch/v1","pkg/apis/batch/v2alpha1","pkg/apis/certificates","pkg/apis/certificates/v1beta1","pkg/apis/extensions","pkg/apis/extensions/v1beta1","pkg/apis/policy","pkg/apis/policy/v1beta1","pkg/apis/rbac","pkg/apis/rbac/v1alpha1","pkg/apis/rbac/v1beta1","pkg/apis/settings","pkg/apis/settings/v1alpha1","pkg/apis/storage","pkg/apis/storage/v1","pkg/apis/storage/v1beta1","pkg/util","pkg/util/parsers","pkg/version","plugin/pkg/client/auth","plugin/pkg/client/auth/gcp","plugin/pkg/client/auth/oidc","rest","rest/watch","testing","third_party/forked/golang/template","tools/auth","tools/clientcmd","tools/clientcmd/api","tools/clientcmd/api/latest","tools/clientcmd/api/v1","tools/metrics","transport","util/cert","util/clock","util/flowcontrol","util/homedir","util/integer","util/jsonpath"] | ||
revision = "21300e3e11c918b8e6a70fb7293b310683d6c046" | ||
version = "v3.0.0" |
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 for 1.6 Kubernetes, does it mean that more recent features like CRDs are not supported?
Convert from govendor to dep.
note: this updates a few packages as well.
Signed-off-by: bryanl [email protected]