fix(scheduler): pass down the right variable for Deployment revision history limit (#1037)

Prior to this the wrong variable was being passed and as such the revision history feature did not work

Author: helgi

rootfs/api/models/app.py

@@ -540,7 +540,7 @@ def deploy(self, release, force_deploy=False):
                 'routable': routable,
                 'deploy_batches': batches,
                 'deploy_timeout': deploy_timeout,
-                'deployment_history_limit': deployment_history,
+                'deployment_revision_history_limit': deployment_history,
                 'release_summary': release.summary,
                 'pod_termination_grace_period_seconds': pod_termination_grace_period_seconds,
                 'image_pull_secret_name': image_pull_secret_name,

rootfs/scheduler/resources/deployment.py

@@ -94,8 +94,8 @@ def manifest(self, namespace, name, image, entrypoint, command, **kwargs):
         }
 
         # Add in how many deployment revisions to keep
-        if kwargs.get('deployment_revision_history', None) is not None:
-            manifest['spec']['revisionHistoryLimit'] = int(kwargs.get('deployment_revision_history'))  # noqa
+        if kwargs.get('deployment_revision_history_limit', None) is not None:
+            manifest['spec']['revisionHistoryLimit'] = int(kwargs.get('deployment_revision_history_limit'))  # noqa
 
         # tell pod how to execute the process
         kwargs['command'] = entrypoint