Secrets backend choosing doesn't seem to work

[petemounce]

On linux, attempting to specify a secret-backend other than kwallet (which isn't installed, because people tend to not use KDE here) fails:

# me on my-box in ~/mydir on git:master ✖︎ [10:04:40]
→ go run cmd/bk/main.go configure buildkite
──── Configuring Buildkite GraphQL credentials

Create a GraphQL token at https://buildkite.com/user/api-access-tokens/new. Make sure to tick the GraphQL scope at the bottom.

GraphQL Token: me@here.com ✅

�� The name org.kde.kwalletd was not provided by any .service files
exit status 1
[1]    2541 exit 1     go run cmd/bk/main.go configure buildkite

# me on my-box in ~/mydir on git:master ✖︎ [10:06:01]
→ go run cmd/bk/main.go configure buildkite --keyring-backend=secret-service
──── Configuring Buildkite GraphQL credentials

Create a GraphQL token at https://buildkite.com/user/api-access-tokens/new. Make sure to tick the GraphQL scope at the bottom.

GraphQL Token: me@here.com ✅

�� The name org.kde.kwalletd was not provided by any .service files
exit status 1
[1]    2918 exit 1     go run cmd/bk/main.go configure buildkite --keyring-backend=secret-service

# me on my-box in ~/mydir on git:master ✖︎ [10:06:44]
→ go run cmd/bk/main.go configure buildkite --keyring-backend=file          
──── Configuring Buildkite GraphQL credentials

Create a GraphQL token at https://buildkite.com/user/api-access-tokens/new. Make sure to tick the GraphQL scope at the bottom.

GraphQL Token: me@here.com ✅

�� The name org.kde.kwalletd was not provided by any .service files
exit status 1
[1]    3048 exit 1     go run cmd/bk/main.go configure buildkite --keyring-backend=file

# me on my-box in ~/mydir on git:master ✖︎ [10:07:04]
→ go run cmd/bk/main.go --keyring-backend=file configure backend
�� unexpected backend
exit status 1
[1]    3225 exit 1     go run cmd/bk/main.go --keyring-backend=file configure backend

# me on my-box in ~/mydir on git:master ✖︎ [10:07:09]
→ go run cmd/bk/main.go --keyring-backend=file configure buildkite
──── Configuring Buildkite GraphQL credentials

Create a GraphQL token at https://buildkite.com/user/api-access-tokens/new. Make sure to tick the GraphQL scope at the bottom.

GraphQL Token: me@here.com ✅

�� The name org.kde.kwalletd was not provided by any .service files
exit status 1
[1]    3378 exit 1     go run cmd/bk/main.go --keyring-backend=file configure buildkite

[lox]

Thanks for the heads up, I'll check it out. I wonder why emoji is rendering as �� for you.

[petemounce]

That was a copy paste via slack from linux. I'm ok with the emoji not surviving that gauntlet ;)

[irlevesque]

@lox - as mentioned today, this is the bug affecting us. It would be great to be able to run the CLI on our Linux machines. Let me know if I can help with testing/debugging.

[lox]

Apologies for the delay folks, just investigating this now. This issue is extremely relevant: 99designs/keyring#12

I'm tempted to just entirely disable secret-service and kde upstream, or in this project.