New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can create a flow without ID through REST API #3646
Comments
@zregvart @lburgazzoli What are your thoughts on this? |
There are quite a number of things that can go wrong by using the rest interface directly because as today most of the checks are done by the UI. As we do not expose the REST interface to users, I'm keen to see this as not a problem. We need to revisit this once we decide to open the REST interface outside the UI. |
#techdebt we should validate all parameters we receive via the REST API. A bunch of this we get with Immutables if we turn on JSR 303 validations. |
ok, thanks for the feedback. We leave it open for further consideration but will not (yet) act on it. |
@jstastny-cz I think this one of the areas where we would love to see contributions. If you can think about adding further constraints to the API parameters, I guess @zregvart can point you in the right direction. |
The API is for internal use only. Closing this for now. |
This is a bug.
User (through REST API) can create an Integration with Flow which doesn't have id specified. The Integration is created, and works well.
But when trying to edit the Integration through web interface, the flow is not visible after clicking 'Edit integration' and all the screen seems broken (no buttons or links).
Either the Flow id needs to be enforced via REST API, or web interface need to overcome this deficiency.
The text was updated successfully, but these errors were encountered: