Add the ability to turn off image pulling.

To be clear, Go-style says acronyms are consistent-case, so things like TCP
will stay TCP, not Tcp.

Thanks for a decision - if you have context can you file issues for things
that are not conformant?  I started a PR, but I dunno if I have bandwidth
to finish it right now.  I can post it if someone wants to run with it.

On Fri, Sep 26, 2014 at 5:40 PM, bgrant0607 <notifications@github.com>
wrote:

> In pkg/api/types.go:
>
> > @@ -173,6 +173,16 @@ type LivenessProbe struct {
> >  	InitialDelaySeconds int64 `yaml:"initialDelaySeconds,omitempty" json:"initialDelaySeconds,omitempty"`
> >  }
> >
> > +// PullPolicy describes a policy for if/when to pull a container image
> > +type PullPolicy string
> > +
> > +const (
> > +	// Always attempt to pull the latest image
> > +	PullNewest PullPolicy = "PULL_NEWEST"
>
> Current situation:
>
>    - PodStatus is capitalized.
>    - Status.Status is lowercase.
>    - StatusReasons are lowercase, with underscores.
>    - CauseTypes are Java-style camelCase.
>
> I haven't seen any JSON-based APIs that use all uppercase. They use some
> flavor of camel case or all lowercase with underscores. I also find all
> uppercase excessively attention-grabbing and space-consuming in the case of
> variable-width fonts.
>
> Using Java-style camelCase makes string constants look like json fields.
> Using Go-style makes them look like types, which emphasizes their static
> nature and similarity to constants represented as structs. It also makes
> them more readable. We're going to be displaying status values, causes,
> reasons, etc. in the CLIs and UIs.
>
> Example:
>
>    - fieldValueInvalid
>    - FieldValueInvalid
>    - field_value_invalid
>    - FIELD_VALUE_INVALID
>
> Decision: Go-style CamelCase.
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/kubernetes/pull/1458/files#r18120478>
> .
>