`jobSubmit` alters `Destination`, regardless of what is defined in `job-settings.json`

[amureki]

Describe the bug A solution documentation states that the jobSubmit lambda function applies settings defined in job-settings.json and submits a job to AWS MediaConvert. Reality is different, and the jobSubmit lambda function alters settings and overrides the destination of the resulting files.

To Reproduce

1. Set up the solution via AWS CloudFormation template
2. Alter job-settings.json file to change Destination setting (for example, to destinationbucket/videos/$fn$). $fn$ here stands for a defined variable.
3. Upload video and see that the processed files were uploaded to destinationbucket/guid/AppleHLS1/ regardless of what was defined above.

Expected behavior Resulting files uploaded to destinationbucket/videos/$fn$

Please complete the following information about the solution:

• [x] Version: v1.3.0
• [x] Region: eu-central-1
• [x] Was the solution modified from the version published on this repository? // Modified job-settings.json
• [x] If the answer to the previous question was yes, are the changes available on GitHub? // Not available, but the example is defined right above
• [x] Have you checked your service quotas for the sevices this solution uses? // No issues with quotas
• [x] Were there any errors in the CloudWatch Logs? // No errors in the logs

[raulmlamzn]

Thank you for your suggestion. We will consider your feedback and have added this request to our backlog for this solution.