Issue with private python library and LangGraph Platform deployment #2426
majorgilles
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, I already posted in langgraph-cloud-help but received no help yet.
do you know if it's possible to trigger a langgraph-cloud (so, hosted 100% by langgraph) via an langgraph CLI call? reason being we need to generate some token dynamically, and I don't think we can write scripts in the langgraph cloud UI to do that for us as part of the deployment process (when creating a new revision, for example, it would need a new token to authorize download some private company artifcat / library)
new deployments + revisions are having issues with Env variables:
I have a working configuration for the dockerisation process in langgraph_studio with a script that copies an env variable in .env:
with an .env that looks like that:
LangGraph Studio is working fine with this setup and is correctly able to build the docker image and download the artifact.
Yet when I input the CODEARTIFACT_AUTH_TOKEN which is required for the build to function in LangGraph cloud, it's not able to correctly auth to my private repository (edited)
I'm setting this env variable manually just like any other env variable:
I added some lines to RUN echo 'this is the token: ' + $CODEARTIFACT_AUTH_TOKEN and it doesn't show up!
=> when I click on "New revision", despite having tried to add $CODEARTIFACT_AUTH_TOKEN env varible, the CODEARTIFICAT_AUTH_TOKEN appears not to be saved, I need to add it AGAIN via the "+ Add" button.
I have the same issue with new deployments for which I've set env variables, they don't seem to be persisted at all:
I didn't have that issue before when I created my initial deployments a few weeks ago.
Beta Was this translation helpful? Give feedback.
All reactions