Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Importing integrations sharing the same extension duplicates the extension #5163

Open
tadayosi opened this issue Apr 9, 2019 · 2 comments
Open
Labels
notif/triage The issue needs triage. Applied automatically to all new issues. status/never-stale Marker that this issue should not be marked as stale

Comments

@tadayosi
Copy link
Contributor

tadayosi commented Apr 9, 2019

This is a...


[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Documentation issue or request

Description

Say we have two integrations both of which use Set Body extension. Exporting and re-importing them tries to import duplicate Set Body extensions, which causes broken states in the imported integrations.

Ideally, Syndesis should check the extension's identifier (groupId & artifactId & version) and if it's identical with the existing one Syndesis should use it instead of re-importing a duplicate one.

duplicate extensions

See Set Body and Set Body-imported-1.

duplicate-extensions

broken state in the imported integration

See the second step with a broken icon.

broken-state

@pure-bot pure-bot bot added the notif/triage The issue needs triage. Applied automatically to all new issues. label Apr 9, 2019
@stale
Copy link

stale bot commented Jul 8, 2019

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

@stale stale bot added the status/stale Issue considered to be stale so that it can be closed soon label Jul 8, 2019
@tadayosi
Copy link
Contributor Author

I think still it should be addressed.

@stale stale bot removed the status/stale Issue considered to be stale so that it can be closed soon label Jul 12, 2019
@zregvart zregvart added the status/never-stale Marker that this issue should not be marked as stale label Jul 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
notif/triage The issue needs triage. Applied automatically to all new issues. status/never-stale Marker that this issue should not be marked as stale
Projects
None yet
Development

No branches or pull requests

2 participants