WIP: Deployment Triggers POC

Making a PR for this to make tracking comments easier.
I think in this case the upstream pattern buys you nothing - Config structs are really for > 3-4 fields.

----- Original Message -----
> > +	kapi "github.com/GoogleCloudPlatform/kubernetes/pkg/api"
> > +	"github.com/GoogleCloudPlatform/kubernetes/pkg/api/errors"
> > +	"github.com/GoogleCloudPlatform/kubernetes/pkg/util"
> > +	"github.com/golang/glog"
> > +	osclient "github.com/openshift/origin/pkg/client"
> > +	deployapi "github.com/openshift/origin/pkg/deploy/api"
> > +	deployutil "github.com/openshift/origin/pkg/deploy/util"
> > +)
> > +
> > +// A DeploymentConfigController is responsible for implementing the
> > triggers registered by DeploymentConfigs
> > +type DeploymentConfigController struct {
> > +	config *Config
> > +}
> > +
> > +// Holds the configuration of a DeploymentConfigController
> > +type Config struct {
> 
> This was mostly about following the upstream pattern.
> 
> @ironcladlou Do you still feel strongly about having config objects?  We
> could keep the factories and have them make the controllers rather than the
> configs and get about the same factoring.  It would also simplify the tests.
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/openshift/origin/pull/133/files#r18860938