mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 09:25:49 +03:00
[GH-ISSUE #543] Secret Management for the spotify connect token #315
Labels
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-player#315
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Mcrtin on GitHub (Aug 14, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/543
Is your feature already implemented in the latest
master?I don't think so, but please show me otherwise.
Is your feature request related to a problem? Please describe.
I'm using Spotify-player with home-manager for a declarative config. However, I don't want to leak my secrets in my config, because the get evaluated and put into the world-readable nix store.
Describe the solution you'd like
Add a 'token command' field like spotifyd's 'password_cmd' or neomutt's 'account_command' (https://neomutt.org/feature/account-cmd)
Describe alternatives you've considered
Not putting the key in the upstream repo.
Additional context
I'm using nixos + home-manager + sops-nix
@aome510 commented on GitHub (Aug 17, 2024):
For secret, do you mean
client_id? Should be addressed by https://github.com/aome510/spotify-player/pull/548play,pause, andgenerateCLI commands #714playback playandplayback pause#1102play,pause, andgenerateCLI commands #1650