Answered

Conflict when pulling snapshot of integration to a clone

Philippe Foisy

August 04, 2022 17:09

Hi there,

So we have an integration that we clone to create dozen of integrations (each using different connections). Lately, I've been modifying this "template" integration to add additional flows.

Now that I'm confident that my changes can now be pulled into the cloned integrations, I snapshotted the "template" integration and I'm now trying to pull that image onto my cloned integration. I'm facing a frustrating conflict regarding the /debugUntil field

Frustrating because I cannot simply "empty" this field before snapshoting / pulling.

How can I help you help me fix this situation ?

Comments

5 comments

viliandy leonardo
August 04, 2022 17:38 (Edited August 04, 2022 18:16)

Product Management Director

Philippe Foisy

I want to make sure I understand what happened: when you try to merge the changes from the "template" integration into the clone, you run into conflict due to "/debugUntil" field. Is the issue you cannot resolve the conflict manually?

I suggest that you log a support ticket so we can investigate this further and we'll help to set the value for you. We'll look into fixing this so that we don't take into account /debugUntil value as a conflict. Thanks

0
Philippe Foisy
August 04, 2022 17:45

Hi viliandy leonardo,

That's exactly it. I didnt create a ticket as I wasnt sure I wasn't my own problem :)

Regards

0
Philippe Foisy
August 04, 2022 19:18

I submitted a ticket, see ID122952

Thx in advance

0
Philippe Foisy
August 10, 2022 20:10
Good afternoon everyone,

After discussing with the Celigo Team, I was given a temporary workaround while the Celigo team works on omitting the /debugUntil field in the merge process.

Before snapshotting a "template" integration, you have to "patch" all the exports / imports to remove their respective /debugUntil fields. To do that, a REST API request is required :
```
PATCH https://api.integrator.io/v1/exports/<exportID>

Authorization: Bearer <bearertoken>

Body:
[
   {
       "op": "remove",
       "path": "/debugUntil"
   }
]
```
Doing this cleanup, doing a snapshot, and then pulling the snapshot on the cloned integration resulted in no merge conflicts.
0
viliandy leonardo
August 10, 2022 20:31

Product Management Director

Philippe Foisy

Thank you for sharing. We are targeting to have the fix released as part of r3 release time line - ETA mid September.

Vili

0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post