topic Re: Hi Everyone, in Workato Pros Discussion Board

Hi Everyone,

soniya-singhal — Mon, 08 Feb 2021 13:08:59 GMT

We have a use case for CI/CD intregaration on workato. So any one can help on this.

Re: Hi Everyone,

viswanathan-r — Mon, 08 Feb 2021 13:10:46 GMT

Even Im also started working on the same usecase

Re: Hi Everyone,

vmendhe — Mon, 08 Feb 2021 13:12:53 GMT

Would be interested to know about it!

Re: Hi Everyone,

soniya-singhal — Mon, 08 Feb 2021 14:21:51 GMT

thats great..so can you please share some referneces to intregarte or to start on this use case

Re: Hi Everyone,

soniya-singhal — Mon, 08 Feb 2021 14:23:43 GMT

Hemanth Kumar

Re: Hi Everyone,

viswanathan-r — Mon, 08 Feb 2021 14:33:22 GMT

We dont have reference as such, what we have planned as a intial stage,

1. we ask the user to choose the manifest to be deployed from Slack bot

2. Export the manifest and download the package into some repo.

3. Then from another environment we import the package and deploy it

We still in step 2.

This is document we currently have https://docs.workato.com/workato-api/recipe-lifecycle-management.html.

Re: Hi Everyone,

soniya-singhal — Mon, 08 Feb 2021 16:41:39 GMT

Thank you for info...One more question do you know manifest list API release date?

Re: Hi Everyone,

rak-9177 — Mon, 08 Feb 2021 16:46:25 GMT

We just recently implemented CI/CD using buildkite but deleted/moved recipes won’t work in CI/CD.

Re: Hi Everyone,

rak-9177 — Mon, 08 Feb 2021 16:51:58 GMT

Deleted recipes should be handled manually similar to recipe life cycle management which is not possible.

Re: Hi Everyone,

csinghal — Mon, 08 Feb 2021 17:26:40 GMT

you can export manifest file and download into your repo.

Re: Hi Everyone,

gwilkinson — Mon, 08 Feb 2021 20:09:11 GMT

One thing to be mindful of is the enhancement to add formal "environments" capability to Workato and the impact to any CI/CD solution. I believe manifests are going away as part of this enhancement (not entirely sure).

Re: Hi Everyone,

deven-maru — Tue, 09 Feb 2021 13:05:03 GMT

Soniya Singhal what source control management and continuous integration (CI) stack do you have? What you can do is to leverage the Workato platform APIs (https://docs.workato.com/workato-api) specifically the folders and recipe lifecycle management APIs to automate the CI/CD pipeline.

You can kickoff the CI process from Workato using a scheduler or start the process manually in your CI script. As part of the CI script you can use the recipe lifecycle management APIs to export and then download the package. If your source control management supports APIs for committing then you can use the CI script to commit the downloaded Workato package, unpack it and commit both the .zip file and the unpacked recipe .json files to the source control. Next, is change review and approval of the change. This can happen in source control like GitHub where you can create the pull request (PR) for review. Upon PR approval, you can kick off the deployment of the Workato package to the next environment using the import API.

Gary Wilkinson the new deployment flow will not require creating a manifest. But we will continue to support the manifest and export/import lifecycle steps for foreseeable future.

Re: Hi Everyone,

soniya-singhal — Tue, 09 Feb 2021 13:53:04 GMT

Deven Maru thank you for info.

We are using Bitbucket as source control

Re: Hi Everyone,

gwilkinson — Tue, 09 Feb 2021 20:46:57 GMT

Deven Maru thanks, good to know.

Re: Hi Everyone,

mroldanvega — Mon, 13 Feb 2023 19:44:24 GMT

Curious to know if anyone ever implemented it successfully since this thread is from 2021.