You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
Currently the "New route" button adds multiple CRDs for Integration, Kamelet and KameletBinding. Since multiple CRDs require bigger consideration for having multiple contexts, we decided to
Integration kind: Add routes in the existing CRD
Kamelet kind: Disable New route
KameletBinding: Disable New route
Until we fully support multiple contexts.
Steps to Reproduce the Bug or Issue
Choose Integration, Kamelet or KameletBinding
Click New route button
Screenshots or Videos
No response
Platform
OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 0.30.0]
The text was updated successfully, but these errors were encountered:
Currently, there's a `supportsMultipleFlows` property from the capabilities
endpoint from the backend that the UI is not leveraging yet.
This property is meant to signal the UI whether a DSL supports multiple
flows or not.
This pull request makes use of the said property to disable the
New route button in case the UI is dealing with those kinds of DSL.
At the moment of writing this code, those DSLs are `Kamelet` and `KameletBindings`
fixes: #2055
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the Bug
Currently the "New route" button adds multiple CRDs for
Integration
,Kamelet
andKameletBinding
. Since multiple CRDs require bigger consideration for having multiple contexts, we decided toNew route
New route
Until we fully support multiple contexts.
Steps to Reproduce the Bug or Issue
Integration
,Kamelet
orKameletBinding
New route
buttonScreenshots or Videos
No response
Platform
The text was updated successfully, but these errors were encountered: