Remove job_exec_data argument

The job_exec_data field was added to handle diverging schemas
for job executions.  With the addition of "edp." config settings
to handle job-type-specific data fields, this argument is no
longer needed.

Change-Id: I3ec277b6b407aa01784d4303bfa409dafdcbdeeb
Partial-implements: blueprint edp-config-parameter-prefix

savannaclient/api/job_executions.py

@@ -13,7 +13,6 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-import copy
 from savannaclient.api import base
 
 
@@ -33,10 +32,12 @@ class JobExecutionsManager(base.ResourceManager):
     def delete(self, obj_id):
         self._delete('/job-executions/%s' % obj_id)
 
-    def create(self, job_id, cluster_id, input_id, output_id, configs,
-               job_exec_data={}):
+    def create(self, job_id, cluster_id, input_id, output_id, configs):
         url = "/jobs/%s/execute" % job_id
-        data = copy.copy(job_exec_data)
+        data = {
+            "cluster_id": cluster_id,
+            "job_configs": configs
+        }
 
         # Leave these out if they are null.  For Java job types they
         # are not part of the schema
@@ -46,11 +47,4 @@ class JobExecutionsManager(base.ResourceManager):
             if value is not None:
                 data.update({key: value})
 
-        # These are always required
-        data.update(
-            {
-                "cluster_id": cluster_id,
-                "job_configs": configs
-            })
-
         return self._create(url, data, 'job_execution')