WIP: deployments POC



> On Sep 12, 2014, at 12:35 PM, Andy Goldstein <notifications@github.com> wrote:
> 
> In pkg/deploy/api/v1beta1/types.go:
> 
> > +const (
> > +	DeploymentNew      DeploymentStatus = "new"
> > +	DeploymentPending  DeploymentStatus = "pending"
> > +	DeploymentRunning  DeploymentStatus = "running"
> > +	DeploymentComplete DeploymentStatus = "complete"
> > +	DeploymentFailed   DeploymentStatus = "failed"
> > +)
> > +
> > +// A Deployment represents a single unique realization of a DeploymentConfig.
> > +type Deployment struct {
> > +	api.JSONBase       `json:",inline" yaml:",inline"`
> > +	Labels             map[string]string              `json:"labels,omitempty" yaml:"labels,omitempty"`
> > +	Strategy           DeploymentStrategy             `json:"strategy,omitempty" yaml:"strategy,omitempty"`
> > +	ControllerTemplate api.ReplicationControllerState `json:"controllerTemplate,omitempty" yaml:"controllerTemplate,omitempty"`
> > +	Status             DeploymentStatus               `json:"status,omitempty" yaml:"status,omitempty"`
> > +	ConfigID           string                         `json:"configId,omitempty" yaml:"configId,omitempty"`
> @pmorie & I went back and forth on label vs field. Doesn't it make more sense to strongly define it as a field?
> 
It's an open question upstream.  I'd argue to be more consistent with upstream for now - we can always migrate it later.
> —
> Reply to this email directly or view it on GitHub.