replicas set to 0 if not specified

[kadel]

If replicas is not set in Kedge file, the generated output shouldn't have it either.

Now it defaults to 0, which leads to a confusing situation where your containers are not started when DC id deployed.

name: foo
controller: deploymentconfig
containers:
  - image: quay.io/tomkral/sleeper

▶ ./kedge generate -f test.yaml
---
apiVersion: v1
kind: DeploymentConfig
metadata:
  creationTimestamp: null
  name: foo
spec:
  replicas: 0
  strategy:
    resources: {}
  template:
    metadata:
      creationTimestamp: null
    spec:
      containers:
      - image: quay.io/tomkral/sleeper
        name: foo
        resources: {}
  test: false
  triggers: null
status:
  availableReplicas: 0
  latestVersion: 0
  observedGeneration: 0
  replicas: 0
  unavailableReplicas: 0
  updatedReplicas: 0

replicas shouldn't be set if it's not set in Kedge file, OpenShift default will be used on the cluster side.

[surajssd]

@kadel the structs we are importing should have omitempty in structtag

https://github.com/surajssd/kedge/blob/3ade8541e2209148c21c636464e12aea75e35e3a/vendor/github.com/openshift/origin/pkg/deploy/apis/apps/v1/types.go#L50

[surajssd]

We are not setting the value anywhere inside the code!

[kadel]

If there is no other solution than We will have to default to 1 manually.

But we have to be careful and correctly recognize if replicas in kedge wasn't set or it was explicitly set to 0

[cdrage]

@kadel @surajssd

I originally had this in the code, you can access replicas by reading in the variable deploymentConfig.Replicas

Checking to see if the default is 0 and change it to 1..