Need Help with Dagger CLI: Error - Secret Not Found

[strong palm]

Hello,

I'm currently using the Dagger CLI to set a secret and retrieve it, but I encountered an error saying "Error: secret not found." I've included the script I'm using below. Could you please help me identify what might be going wrong?

Thank you!

#!/usr/bin/env bash

REGISTRY_PASSWORD="monsecret"


registry_secret_id=$(dagger query <<QUERY | jq -r '.setSecret.id'
{
   setSecret(name: "registry-password", plaintext: "$REGISTRY_PASSWORD") {
     id
   }
}
QUERY
)
echo -e "$registry_secret_id"

dagger query <<QUERY
{
  secret(id: "$registry_secret_id") {
    plaintext
  }
}
QUERY

[sweet totem]

👋 this is because secrets are only re-usable withing the same dagger session. Since you're running dagger query twice, that creates two different sessions.

If you run dagger run <your_script.sh> that will make both dagger query to use the same session since the session is started by dagger run

hmm just realized dagger query doesn't re-use the same session if it exists.. probably a defect from our side

checking with @feral stream just to validate dagger query should re-use a session if invoked with dagger run

[feral stream]

I don't think it will, it just starts its own engine each time

[sweet totem]

yep, that's what I saw.. but I think that's a miss from our side? I was expecting to re-use a session if ran within docker run

@strong palm what you can do in the meantime is follow this approach Helder described in another post of replacgin dagger query with a query function that just uses curl to call the graphql API. #1110544435781050418 message

[feral stream]

sounds like a reasonable feature request; I don't think any of the dagger commands respect an existing session, they all create one

[sweet totem]

well.. there's only dagger run and dagger query, and dagger run is the "session bootstrapper" 😛

[feral stream]

right now they're all session bootstrappers 😛 (there's also dagger session and dagger listen)

[strong palm]

so does it mean I cannot use secrets?

[feral stream]

not with dagger query. Is there a reason you're not using a SDK? Maybe it's not supported for your preferred language?

[strong palm]

it's supported by my preferred language but it's not by the team i'm working with

[sweet totem]

true.. forgot about hidden commands

[sweet totem]

you can follow the example I posted about and use curl instead of dagger query

[strong palm]

I have done every steps I needed but one which is to publish to the registry and I need to authenticate this is why i needed to use secret

[feral stream]

do you mean the language your team prefers isn't supported?

just trying to understand, it seems to me like using any language would be better than scripting GraphQL APIs with bash haha

[strong palm]

I agree but if I start doing it in go or python nobody is going to maintain it

alright, thank you for your help

[sweet totem]

I'll open an issue to make dagger query re-use a session if it exists

[strong palm]

I used curl and it's working... thank you