Description

Please include a summary of the change being made.

Fixes#117 and#171

Why is the change necessary?

Currently, it is not possible to use placeholders for Sagemaker Transform properties. The properties cannot be defined dynamically, as they need to be defined in the Transformer which does not accept placeholders.
This change makes it possible to use placeholders for Transform properties by using theparameters field that are passed down from the TransformStep.

Solution

Use theparameters field that is compatible with placeholders to define TrainingStep properties.
Merge the parameters that were generated from theTransformer with the input parameters:

• The input parameters will overwrite the parameters generated from the Transformer if the properties were defined in both
• All TransformStep properties will be placeholder compatible
• The input parameters should follow the schema described inCreateTransformJob API doc

• Same solution was adopted forfeat: Support placeholders for processing step

Testing

Added integration and unit tests

Pull Request Checklist

Please check all boxes (including N/A items)

Testing

• Unit tests added
• integration test added

Documentation

• docs: All relevantdocs updated
• docstrings: All public APIs documented

Title and description

• Change type: Title is prefixed with change type: and followsconventional commits
• References: Indicate issues fixed via:Fixes #xxx

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.