Importing existing flows created/updated with Architect UI

[irwin]

This tool is looking great! Would be awesome to get call flows checking into version control!

I am wondering if any thought has been given to adding a feature for importing and refreshing existing flows?

For example importing a flow that was originally created via the Architect UI or refreshing a flow that was created via Archy but later edited via Architect UI, causing drift in running config vs local YAML.

This type of feature would greatly ease the adoption of the tool and get you jump started as you can pull in all of your existing flows without having to convert/recreate them. Also if you were stuck on how to create a specific flow process but knew how to do it in the UI, you could create it there and then import it to generate the needed syntax.

Potentially this could be an extension of the 'refresh' command where it pulls in the current state of the flows that were created/imported and then an import command to pull in specific existing flow(s).

Now that I think on it more.. much of the thoughts on this comes from how I use Terraform today. In fact, a terraform provider for Genesys would be pretty awesome... but obviously that is another topic all together!

Anyway, great work on this! Looking forward to additional features and the eventual GA release.

[jon.vansteen]

Hi @irwin,

I'm glad to hear you are liking Archy! We are actually working on a feature to export a flow from the Architect UI into a YAML format, which would allow you to then use this flow with Archy. This would allow you to create a YAML file with any new changes you have in your flow. This functionality may also get ported into Archy itself as you had talked about. Theres currently no release date for this feature but it's in the works!

Thanks for the feedback!
Jon

[irwin]

Thank you for the response! That is great to hear!

[Adam]

So glad you're working on this!! I just spent a few hours becoming familiar with Archy. It will solve so many automation problems for us. But I couldn't imagine creating a flow directly in yaml, so exporting flows from architect (or directly via Archy) is a must-have IMHO.