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
The user needs to know pipeline id to interact with it via the Rest API, e.g., send data with curl. Currently, it needs to be extracted from the URL in the browser or from the log. It would be nice to show it inside the UI.
in builder you can just grab it from URL I think that's acceptable?
the thing with displaying it in the builder is that there is a time (when the pipeline doesn't exist yet) where there is no id for it yet (until the first time it's saved) so then it would suddenly pop-up.. not terrible, but also not great IMO
I am not sure putting IDs everywhere in the UI is the way to go -- ideally the point of the UI should be to reduce some complexity (for one thing you don't have to deal with IDs), so putting ids back everywhere defeats the purpose a bit, of course there is a fluent boundary between UI usage and CURL/SDK usage but I think it's ok to expect some "advanced" skills like reading a ID from a URL or from the config tab (or use REST to query by name to find it the id) if one wants to use the REST API
Activity
gz commentedon Aug 17, 2023
we should probably put it in configuration here:

ryzhyk commentedon Aug 17, 2023
This was my first instinct, but the config is only displayed when the pipeline is running.
gz commentedon Aug 17, 2023
for most of the REST/CURL things you would do, e.g., to send data you'd need pipeline running so this should be fine if only visible then?
(we could also make it a hidden column in the table that can be enabled (always show it seems a bit noisy as the id's are quite long))
ryzhyk commentedon Aug 17, 2023
Perhaps it could also be displayed in the pipeline builder?
gz commentedon Aug 17, 2023
in builder you can just grab it from URL I think that's acceptable?
the thing with displaying it in the builder is that there is a time (when the pipeline doesn't exist yet) where there is no id for it yet (until the first time it's saved) so then it would suddenly pop-up.. not terrible, but also not great IMO
I am not sure putting IDs everywhere in the UI is the way to go -- ideally the point of the UI should be to reduce some complexity (for one thing you don't have to deal with IDs), so putting ids back everywhere defeats the purpose a bit, of course there is a fluent boundary between UI usage and CURL/SDK usage but I think it's ok to expect some "advanced" skills like reading a ID from a URL or from the config tab (or use REST to query by name to find it the id) if one wants to use the REST API
ryzhyk commentedon Aug 17, 2023
fair enough
Display ID in configuration.