LNTWOOL Comments - BuildShip

LNTWOOL

•Created by LNTWOOL on 12/27/2024 in #💬・general

LNTWOOL - the pains with buildship continue. So...

ah thank you, yes i can now use the end point. thanks

11 replies

•Created by LNTWOOL on 12/27/2024 in #💬・general

LNTWOOL - the pains with buildship continue. So...

hello any update??? i simply need to reclaim the api endpint /linked/kai.. this is a bug, it has been deleted, it should not still be there @Harini

11 replies

•Created by LNTWOOL on 12/27/2024 in #💬・general

LNTWOOL - the pains with buildship continue. So...

Endpoint meaning /linked/kai in my environment. That was deleted obviously when i deleted the entire flow, yet buildship says it's still there, it's been a week

11 replies

•Created by LNTWOOL on 12/27/2024 in #💬・general

LNTWOOL - the pains with buildship continue. So...

And at this point im not even asking for it to be restored (that would be nice), but the expected behavior if it's deleted, then i should be able to use the deleted flow's API trigger endpoint, but build ship will not let me, it says it another flow has it. I have run into this twice before, i delete an entire flow, i try to use the API trigger end point that was deleted, and i can't

11 replies

•Created by LNTWOOL on 12/27/2024 in #💬・general

LNTWOOL - the pains with buildship continue. So...

How do i get that if its deleted?

11 replies

•Created by LNTWOOL on 12/27/2024 in #💬・general

LNTWOOL - the pains with buildship continue. So...

well ill just do it, here, is this what you need. project id: buildship-0nfjbb, bucket_id: buildship-0nfjbb-us-west1

11 replies

•Created by LNTWOOL on 12/27/2024 in #💬・general

LNTWOOL - the pains with buildship continue. So...

DMing now

11 replies

•Created by LNTWOOL on 12/8/2024 in #💬・general

LNTWOOL - So i cannot export a single API i hav...

not exactly, it's feedback for @Harini regarding documenting these things, however the question i had about concurrency or how to handle a token it my situation, i still have not had someone from buildship give me any solution

13 replies

•Created by LNTWOOL on 12/8/2024 in #💬・general

LNTWOOL - So i cannot export a single API i hav...

unlear if the nodes we always used, for example API call, i am just guessing thats a "v1" node, do they intermix with the newer nodes? what implications

13 replies

•Created by LNTWOOL on 12/8/2024 in #💬・general

LNTWOOL - So i cannot export a single API i hav...

theres also no documentation on the custom domain name. had to figure that out myself... you have the the tool tips but they show when your like on the step itself.... if your trying to get into enterprise, they need to know everything upfront to plan, usually there is at least 2 silo'd teams 3 with security that all have to cross communicate something like that

13 replies

•Created by LNTWOOL on 12/8/2024 in #💬・general

LNTWOOL - So i cannot export a single API i hav...

you should add in the documentation, if you make ANY change to the INPUT on your main flow, byebye input value. No warning, nothing. I just randomly found them disappearing... turns out, if i change "required" to "not required" just deletes my variable within the node trigger input

13 replies

•Created by LNTWOOL on 12/8/2024 in #💬・general

LNTWOOL - So i cannot export a single API i hav...

the trigger separation was a big change, and still unclear. I wanted to have multiple rest endpoint's, which i can do, but the schema for the rest endpoint affects the rest of them, and LOGGING, i need to understand what is happening if there is a failure at that trigger level... i did not look into this one too much, but as far as i can tell, but the trigger area is a black box, no clue if something is wrong there

13 replies

•Created by LNTWOOL on 12/8/2024 in #💬・general

LNTWOOL - So i cannot export a single API i hav...

Well, just my opinion - how concurrency is handled, based on my testing its FIFO, the scope of the variables is unclear, for example a workflow variable, is that at the execution scope? or it simply persists for the workflow (which is what i found out). Is there any way to session scoped variables? or expose session information, akin to something like "threadId" from open AI. My use case was a token give from twilo, that every node needed, but only for the session, or i could have done execution. The user dual auth's through an AI agent that is not in build ship, the api fetches the token, then there are 3-4 api calls after that can vary but its not much longer than 3-4 min. So secrets manager seems silly, and writing to a table i just did not want to deal with that headache. So i still don't have a solution. well i do, i am sending the thread id (even though build ship is not hosting the agent) to hash it basically store the variable in the hashed state, then delete it. I can tell you, this is something you are going to need, the community is struggling with agents and authentication in general. There are frameworks coming out, but you could have a big win if you created something specifically for agent auth to services, access to the agent, ,etc

13 replies

•Created by LNTWOOL on 12/8/2024 in #💬・general

LNTWOOL - So i cannot export a single API i hav...

Yeah, i am the founder of https://www.naitive.cloud, we build agents, lots of them. Sometimes we build with the OpenAI nodes, sometimes not, but i basically always use build ship as the tool layer no matter what. We have tooling that builds all of our tools based off the open API spec, but we built it based on exactly how you export api's. Its just a huge time suck, and i have to say the V2 launch has been rough, we've been hit with disappearing inputs, all kinds of weird stuff. It happens, your growing startup we get it. Just the lack of documentation prior to launch has given me a bit of pause to be honest

13 replies

•Created by LNTWOOL on 12/8/2024 in #💬・general

LNTWOOL - So i cannot export a single API i hav...

😦

13 replies

•Created by LNTWOOL on 12/5/2024 in #💬・general

LNTWOOL - Buildships doc's are in dire need of ...

Sorry, did not type correctly. Authenticated user flow: Client -> AI Agent (not in Build Ship) TO BUILDSHIP API's-> BUILDSHIP API's make 4 or 5 outbound (outside of Build Ship) API Calls to a scheduling system, that happen over a roughly 5 minute period that must include bearer token -> Scheduling system API's -> back to Buildship Nodes -> return to AI agent ->AI agent presents to Client

5 replies

•Created by LNTWOOL on 12/5/2024 in #💬・general

LNTWOOL - Buildships doc's are in dire need of ...

Sorry, didn't read through your response... -- To be clear, Authenticated user flow: Client -> AI Agent (not in Build Ship) -> 4 or 5 outbound (outside of Build Ship) API Calls that happen over a roughly 5 minute period that must include bearer token -> AI agent -> Client. -- Authentication Flow: AI Agent (not in build ship) on behalf of the user -> Sends outbound API request to Twilio for the dual auth short code -> The user types dual auth code the user receives via SMS into agent -> Agent verifies by -> another API request to Twilio -> If code is good, the token in question here, a bearer token is returned. So i am not securing my Build Ship API's, I am making outbound API calls to get authenticated for the subsequent API call's from build ship nodes -> to API's outside of build then talk to other API's via Build Ship. My questions has been around sessions concurrency and isolation, but no one has been able to answer the question. So if that question cannot be answered, is there any unique session based, environment variables that maybe i can use to store the variables in a consistant but unique way. The client itself does not do the authentication, thus nothing is sent to Build Ship, thus i have to store it because I'm not storing it on an AI agent. I would this this use case can't be that unique, take the agent out of the equation, for a production API i would think you have a framework around this

5 replies

•Created by LNTWOOL on 12/5/2024 in #💬・general

LNTWOOL - Buildships doc's are in dire need of ...

I agree - such short lived tokens commiting them to a secrets store seemed be alot of overhead. so if i have 300 users, it's not an issue to us built in secret store?

5 replies