The CLI is a great and welcome edition.
It seems to be focused only on Experience assets, unless I’ve missed something. It would be really great if it could be used to sync workflows and (especially) any code embedded in Custom nodes so they could be managed on a local machine and controlled/backed up in a git repository.
Maybe that’s possible with this release or is that a feature suggestion?
Thanks!
HI Paul,
This is definitely a future suggestion, but a great one. I’ll create a ticket and post back when this feature is available.
Thanks,
Erin
Hello,
Is there any update about this suggestion? It’ would be really great to sync workflow with CLI, only to use it with git and check if there was any experience workflow modification before release a new experience version.
Before realase a new experience versions, I have to export the full application, download it, start a git repo, and do the initial commit. Then i copy all the files in the develop version and past into the current version folder, and use the vscode git tools to check wich workflow has changed. But before start checking, i have to run two replaces commands in vscode in order to focus only in signifficant changes, like:
“\s*exportHash.*\n” → “\n”
“version: develop” → “version: ”
So, it would be very faster and efficient to check the workflow changes with CLI.
Thank you.
Hello @Gabriel_Linhares,
I do not have an update about this suggestion. However, the application export process was updated recently to commit an application export directly to a git repository. If you still have the previous copy of your application export, you could commit that to a git repo and then re-export the application to a branch in that repo, then open a pull-request to view your changes. This will show you which resources changed and their changes.
If you are only looking for what changed recently you could compare the date of the previous version made and then sort your develop experience workflows table by last updated, and anything that was updated after the versions are your changed workflows.
If neither of these options work for you could you tell me more about your development process? I ask because you mentioned blocking out exportHash changes to only show significant changes, however if that export hash has changed that would indicate a change to that resource.
Thanks,
Erin