Open zhengqianhe0 opened 1 month ago
The endpoint_name
attribute in the local database table flow
provides an alternative way to identify a flow. It must be a string containing only letters, numbers, hyphens, and underscores, and it is unique per user. This attribute is used in the function get_flow_by_id_or_endpoint_name
to retrieve a flow either by its ID or by its endpoint_name
.
Yes, you can uniquely identify a flow using just the ID. The function get_flow_by_id_or_endpoint_name
first tries to convert the provided identifier to a UUID and fetch the flow by its ID. If the conversion fails, it then attempts to fetch the flow by its endpoint_name
[1].
Regarding the HTTP request when sharing a flow to the store, the endpoint_name
attribute is not included. The attributes included in the request are name
, data
, description
, is_component
, parent
, tags
, private
, and last_tested_version
[2].
To continue talking to Dosu, mention @dosu.
@zhengqianhe0
Do you need any assistance with this case? If not, please let us know if this issue can be closed.
Can you tell me the purpose of the 'endpoint_name' attribute in the local database table 'flow'? This attribute defaults to a null value, and when clicking 'share' to upload my flow to the store, the current flow's endpoint_name attribute was not uploaded in the http request? Now that I have the ID of the flow, can I uniquely identify a flow