kubernetes/pkg/registry
Kubernetes Submit Queue c90faa8071 Merge pull request #44779 from enj/enj/r/etcd_default_name_copy
Automatic merge from submit-queue (batch tested with PRs 44837, 44779, 44492)

Default ObjectNameFunc for all REST Stores

All `Store`s in Kubernetes follow the same logic for determining the name of an object.  This change makes it so that `CompleteWithOptions` defaults the `ObjectNameFunc` if it is not specified.  Thus a user does not need to remember to use `ObjectMeta.Name`.  Using the wrong field as the name can lead to an object which has a name that bypasses normal object name validation.

Signed-off-by: Monis Khan <mkhan@redhat.com>

cc @liggitt @soltysh for review

**Release note**:

```
NONE
```
2017-04-24 07:55:59 -07:00
..
apps Default ObjectNameFunc for all REST Stores 2017-04-21 15:47:25 -04:00
authentication autogenerated 2017-04-14 10:40:57 -07:00
authorization autogenerated 2017-04-14 10:40:57 -07:00
autoscaling Default ObjectNameFunc for all REST Stores 2017-04-21 15:47:25 -04:00
batch Default ObjectNameFunc for all REST Stores 2017-04-21 15:47:25 -04:00
cachesize autogenerated 2017-04-14 10:40:57 -07:00
certificates Default ObjectNameFunc for all REST Stores 2017-04-21 15:47:25 -04:00
core Merge pull request #44779 from enj/enj/r/etcd_default_name_copy 2017-04-24 07:55:59 -07:00
extensions Default ObjectNameFunc for all REST Stores 2017-04-21 15:47:25 -04:00
policy Default ObjectNameFunc for all REST Stores 2017-04-21 15:47:25 -04:00
rbac Default ObjectNameFunc for all REST Stores 2017-04-21 15:47:25 -04:00
registrytest autogenerated 2017-04-14 10:40:57 -07:00
settings Default ObjectNameFunc for all REST Stores 2017-04-21 15:47:25 -04:00
storage Default ObjectNameFunc for all REST Stores 2017-04-21 15:47:25 -04:00
BUILD run generators and updaters 2017-03-01 13:04:29 -08:00
doc.go Use Go canonical import paths 2016-07-16 13:48:21 -04:00
OWNERS add deads2k to registry package owners 2017-02-06 07:41:18 -05:00