Deploying sets desired capacity / running capacity back to 1

[jseppi]

I had a running watchbot service that had scaled up to 5 (the value of maxSize I had set in my template).
I increased maxSize to 10 and redeployed. The service desired and running capacity were reset to 1.

[rclark]

ecs-watchbot/lib/template.js

Lines 400 to 404 in f307ce6

	Resources[prefixed('Service')] = {
	Type: 'AWS::ECS::Service',
	Properties: {
	Cluster: options.cluster,
	DesiredCount: options.minSize,

Recently, the DesiredCount became an optional property in an AWS::ECS::Service. Having it present in the CloudFormation template is what causes stack updates to reset running container counts.

Removing this property entirely ought to solve this issue.

[jseppi]

I think this is the same as #273