98a801a37b
Created batch API group and copied Job there
...
Modeled after on first commit (2fbc5bb#20501 ).
2016-02-19 09:20:56 -08:00
2fbc5bb767
Created autoscaling API group and copied HPA there
2016-02-15 21:39:00 +01:00
c49cd4edf9
Alter the build to generate for __internal correctly
2016-01-22 01:10:22 -05:00
14396fc464
add subject access review types
2016-01-20 08:24:15 -05:00
baf97c9c5e
First use of new deep-copy generator.
2015-12-29 18:06:09 +01:00
5cd5b80f9e
Set up new "metrics" API group.
...
This commit only adds 2 placeholder structs to the API, for the purposes
of separating the API group setup from the API discussion.
2015-11-02 09:49:02 -08:00
e6d3b47eb0
add componentconfig api group to autogen stuff
2015-10-31 11:42:38 -07:00
ccf989a2ae
manual fix hack/after-build/update-generated-deep-copies.sh
2015-10-09 15:38:38 -07:00
cc4ec80ec7
in scripts, experimental/v1alpha1->extensions/v1beta1
2015-10-09 15:19:13 -07:00
ae1293418b
move experimental/v1 to experimental/v1alpha1;
...
use "group/version" in many places where used to expect "version" only.
2015-09-24 15:32:11 -07:00
7a0fc719fb
Fix tooling for apis/experimental's new home
...
* fix package name
* add a script to auto-gofmt everything, useful after grep/sed incantations
* update conversion/deep copy generation
* doc update
2015-09-11 16:06:10 -07:00
00929ed7d8
Convert generated-deep-copies to use golang.org/x/tools/imports
...
I don't like users to need an external binary which can easily get out
of sync. Just include the tools.
2015-08-13 19:36:57 -04:00
eba19cc96a
Add missing argument to function call and don't set GOPATH directly
2015-08-11 21:54:37 -07:00
567bb15432
Generate conversions/deep-copies for experimental. Currently we make (and register) duplicate functions but this is benign.
2015-08-11 17:12:24 -07:00
3b7c39656c
Split hack/{verify,update}-* files so we don't always go build
...
Right now some of the hack/* tools use `go run` and build almost every
time. There are some which expect you to have already run `go install`.
And in all cases the pre-commit hook, which runs a full build wouldn't
want to do either, since it just built!
This creates a new hack/after-build/ directory and has the scripts which
REQUIRE that the binary already be built. It doesn't test and complain.
It just fails miserably. Users should not be in this directory. Users
should just use hack/verify-* which will just do the build and then call
the "after-build" version. The pre-commit hook or anything which KNOWS
the binaries have been built can use the fast version.
2015-08-11 14:20:46 -04:00
Eric Tune