azure-for-dagger/main.go at ce1d338fffd5...

[violet sable]

I think you need to pass in the directory when you make the call, check out some of the example usage

// example usage: "dagger call get-secret --azure-credentials ~/.azure/"

Which specific function are you trying to call and what error(s) are you seeing?

~/.azure/credentials is a relative path to the user that azure agent runs the command as. ~/ is a unix shortcut for /home/$USER where $USER is whatever user you are logged in as

I assume this directory exists by default inside of Azure agent but if thats not the case please provide some more details about your setup and we can dig in further

[deep mural]

it seems the agent has not .azure at the home user. So which makes me thing that i cant use the azure-credentials param like the module suggests. I have been dapping around with finding a way to pipe output in using the cmd:

[violet sable]

@deep mural thanks! Can you tell us more about your setup? Are you using the defaults in azure or doing something custom. I think we'd like to get this example to work for folks so would be great to catch every edge case.

[deep mural]

let me get on my working computer, i was trying to make our "reference build pipeline" implemented in Dagger, but i faced a few issues. give me a moment

[deep mural]

i found a solution

[violet sable]

Great to hear! Can you share what ended up working?

[deep mural]

it was just me having a typo in doing export TOKEN=$(something to get azure container registry token). However there is apperently a module in daggerverse that can check for that .azure directory, but since Azure DevOps is very convoluted how it handles agents, unlike other SCM

[violet sable]

Glad you were able to get this sorted out!