Skip to content
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.

Load balance branches issue - rearanged order after code sync #763

Open
tplevko opened this issue Jul 4, 2023 · 4 comments
Open

Load balance branches issue - rearanged order after code sync #763

tplevko opened this issue Jul 4, 2023 · 4 comments
Labels
bug Something isn't working wontfix This will not be worked on

Comments

@tplevko
Copy link
Contributor

tplevko commented Jul 4, 2023

Describe the Bug

When user tries to use the load-balancer step - the branches are reordered after code sync in code editor. The steps, which were action steps following after the load balance branches are converted to new branches (see recording).
Also the UI adds branches numbers.

Steps to Reproduce the Bug or Issue

  1. create route with load-balance step
  2. create several branches, specify action steps
  3. add following steps to the branches
  4. sync code changes
  5. see the branches reordered

Screenshots or Videos

Peek 2023-07-04 09-23

Platform

  • OS: [e.g. macOS, Windows, Linux]
  • Browser: [e.g. Chrome, Safari, Firefox]
  • Version: [latest]
@tplevko tplevko added the bug Something isn't working label Jul 4, 2023
@igarashitm
Copy link
Contributor

igarashitm commented Jul 5, 2023

It looks like from this doc
https://camel.netlify.app/components/latest/eips/loadBalance-eip.html

load-balance steps should be flat and shouldn't allow adding 2nd(nested) branch steps at first place. It would need to instead create a sub route with direct.

Anyway, frontend should prohibit adding 2nd branch step under load-balance.

@Delawen
Copy link
Member

Delawen commented Jul 11, 2023

Moving to backend to force an end step (add context to mini catalog) the same way REST DSL works so we don't allow more than one step there.

@Delawen
Copy link
Member

Delawen commented Jul 11, 2023

This issue needs KaotoIO/kaoto-ui#1587

@stale
Copy link

stale bot commented Oct 10, 2023

🚨This issue has been automatically marked as stale because it has not had recent activity.🚨
If you are still interested in this issue, please, leave a comment stating its current status. Note that if no development resources has been allocated on it, you may need to search for alternative resources to complete it. It will be closed if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Oct 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants