Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We are storing our task files in Git.
When exporting a task, a date time suffix is being added impeding me to apply versioning.
Can we configure the export format of task file names ? Exporting a task with file name = task name would be the best option. I couldn't find it anywhere.
Thank you.
Hello @Ole_Dufour , copy @Shai_E ,
Not sure how you export the task. if you are using repctl exportrepository command then the option unique_name helps. Comparision with TRUE vs FALSE (in below sample the task name is "Ora-to-ADLS"):
repctl exportrepository task=Ora-to-ADLS unique_name=false
command exportrepository response:
{
"message": "Export succeeded",
"file_path": "C:\\Program Files\\Attunity\\Replicate\\data\\imports\\Ora-to-ADLS.json"
}
[exportrepository command] Succeeded
C:\Program Files\Attunity\Replicate\bin>repctl exportrepository task=Ora-to-ADLS unique_name=true
command exportrepository response:
{
"message": "Export succeeded",
"file_path": "C:\\Program Files\\Attunity\\Replicate\\data\\imports\\Ora-to-ADLS__2023-07-31--22-00-16-683840.json"
}
[exportrepository command] Succeeded
Hope this helps.
Regards,
John.
Hi @Ole_Dufour ,
If i understand correctly you want to export the task json file with the name being only the task without the date?
I do not think this is possible.
The api endpoint for export task on QEM for example exports the task json, but you can see in the name key that it always adds to the task name the date suffix.
Best Regards
Hello @Ole_Dufour , copy @Shai_E ,
Not sure how you export the task. if you are using repctl exportrepository command then the option unique_name helps. Comparision with TRUE vs FALSE (in below sample the task name is "Ora-to-ADLS"):
repctl exportrepository task=Ora-to-ADLS unique_name=false
command exportrepository response:
{
"message": "Export succeeded",
"file_path": "C:\\Program Files\\Attunity\\Replicate\\data\\imports\\Ora-to-ADLS.json"
}
[exportrepository command] Succeeded
C:\Program Files\Attunity\Replicate\bin>repctl exportrepository task=Ora-to-ADLS unique_name=true
command exportrepository response:
{
"message": "Export succeeded",
"file_path": "C:\\Program Files\\Attunity\\Replicate\\data\\imports\\Ora-to-ADLS__2023-07-31--22-00-16-683840.json"
}
[exportrepository command] Succeeded
Hope this helps.
Regards,
John.
Hi @john_wang ,
Yes John i think this is what he is looking for =).
@Ole_Dufour I didnt mention that my comment is strictly for using the QEM api, but through repctl as John mentioned there seems to be a way to do this.
It all depends on how you are exporting the tasks.
Best Regards
In order to export a task I'm just clicking the Export Task button. Will the option unique_name also work for me?
when exporting task from the UI , there is now way to change the format of the task name.
>>> when exporting task from the UI , there is now way to change the format of the task name.
@Steve_Nguyen , @Ole_Dufour I don't get it. You get prompted for a filename to save under.
You can just whack the date/time stamp and replace with something that works with your versioning scheme no? To be sure I just tried with both AEM UI (2023.5.0.130) and Replicate UI (2023.5.0.152).
But really I don't get it that anyone would consider UI steps to deal with versioning and saving exports and changes. For any self respecting developer that stuff _must_ be scripted, either using the AEM API (Powershell, Python,...) or just REPCTL (Bash, CMD, Powershell, Python, Perl,...)
I like the AEM UI just fine, but like any UI it sucks for playbooks and automated versioning, backups and recovery. It's just too error prone for folks to follow the exact steps and new versions may all too easily confuse infrequent users.
Groetjes,
Hein.