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
I made that change but I'm not sure about the value of canExecute when listPipelines is used anonymously. An anonymous user cannot used the initExecution so what would that mean is a pipeline is described to be executable to an anonymous user ? That's why I wrote the canExecute must be false in my PR, as it is clear and logic.
An other solution would be to declare that a canExecute=true pipeline returned to an anonymous mean that it's a public pipeline that is accessible after registration. I would be OK for that.
So that platforms can advertise their pipelines openly.
canExecute
boolean can be customized based on the rights of the (non-)authenticated user.Agreed during meeting.
The text was updated successfully, but these errors were encountered: