bin/docker/composer install
Some transformation files depend on API credentials that are not stored inside the transformations.
You can add these directives on your main-STEP or the transformation you are working on.
In this example "my-account" is used as the account name accross all transformations
account:
name: "my-account"
username: "my-username"
password: "my-password"
domain: "my-domain"
client_id: "my-client-id"
client_secret: "my-client-secret"
You could also add context parameters to your transformation file the same way
context:
my-parameter: "my-value"
Discover all options
bin/docker/console transformation --help
Here is a minimal example of a transformation file:
bin/docker/console transformation --file example/project/transformations/transformation.yaml --source example/project/source --workpath example/project/workpath
Debug the first item that would be written
bin/docker/console transformation --file ... --source ... --workpath ... --debug
try the first 100 items
bin/docker/console transformation --file ... --source ... --workpath ... --try 100
In case you have dynamic mappings, you can show the mappings that would be used
bin/docker/console transformation --file ... --source ... --workpath ... --showMappings
Write only this line, skip the rest
bin/docker/console transformation --file ... --source ... --workpath ... --line 100
Write only this line, skip the rest
bin/docker/console transformation --file ... --source ... --workpath ... --line 100