[Buganizer ID: 461900756] Fix: Pull Playbook Integration Instance Handling in Git Sync

[adarshtwy]

---

What problem does this PR solve?
When importing a playbook using PullPlaybook, if the specific integration instance used in the exported playbook was missing in the target environment, the system failed to select a fallback instance if the available instances were not "configured" (i.e., isConfigured was false). This resulted in steps having no integration instance selected.

How does this PR solve the problem?
We retrieved all instances of the integration on the target platform, not just the configured ones. We then applied the fallback mechanism to select the first instance among them of the same integration type.

Approach to solve the problem
Modified the GitSyncManager._find_integration_instances_for_step method to:

• Include unconfigured instances by removing the filter that excluded instances where isConfigured is false.
• Prioritize configured instances by sorting the list of candidate instances so that configured instances appear first.

Any other relevant information:
This happens because when creating a playbook and selecting a specific environment, the platform currently lacks the option for the user to be able to provide a fall back to a specific integration instance.

However, when creating a playbook and selecting "All Environments," the platform does provide the fallback instance option. We already implemented this fix in one of our earlier releases.

---

[github-actions]

❌ Marketplace Validation Failed

Click to view the full report

---

---

Pre-Build Validation:

Click to view details

🧩 git_sync

Validation Name	Details
⚠️ Uv Lock	Error happened while executing a command: uv lock --check: Using CPython 3.11.14 interpreter at: /opt/hostedtoolcache/Python/3.11.14/x64/bin/python Resolved 66 packages in 1.17s The lockfile at uv.lock needs to be updated, but --check was provided. To update the lockfile, run uv lock.