Kometa-Team/Kometa

Plex Error when utilizing Config Secrets for the plex token

educatedCaveman opened this issue · 17 comments

educatedCaveman commented

Version Number

2.0.2

What branch are you on?

master

Describe the Bug

I'm running Kometa on Kubernetes. I have used the example cronJob manifest as a starting point, and made relatively minor changes to suit my setup (configs linked below). A goal of mine is to keep all my configs under source control (GitHub), and also to not store tokens or API keys in plaintext. To accomplish that, I found the section of the documentation for Config Secrets. I've added a secret containing my various keys for Kometa, and the usage of <<env_var>> seems to work fine. Except for the Plex token. When I run with the plex token obfuscated, it reports:

Plex Error: Plex Token is read only. Please get a new token

I don't think there is an issue with the Plex token because if I hardcode the token, it works perfectly; no error is reported and it does its thing.

I've also verified the environment variable $KOMETA_PLEX_TOKEN returns the token as I entered it when creating the secret.

If it would help to look at my files, they are here. The cronJob manifest is here, and the config creating the error is here.

Relevant Collection/Overlay/Playlist Definition

No response

Logs

https://gist.github.com/educatedCaveman/a0054a551b12df075fc467a401a7cd28

bakerboy448 commented

can confirm Nightly28 is the culprit, it works on 27

suspected RCA ff80a8d

YozoraXCII commented

@educatedCaveman can you confirm if you are seeing this on 2.0.2 or if you are running on develop/nightly? These may be unrelated issues compared to what has been found on the Discord

educatedCaveman commented

@YozoraXCII, yes, I think I can. the logs I've generated reference v2.0.2, and in my cronjob.yml file I have image: kometateam/kometa:v2.0.2