search

David-Maisonave / Axter-Stash

Plugins for Stash (FileMonitor, RenameFile, & DupFileManager)
GNU Affero General Public License v3.0
4 stars 1 forks source link

💡️[Enhancement]: FileMonitor - Support API Key #1

Closed ElCamino-Real closed 3 months ago

ElCamino-Real commented 3 months ago

If feature request is related to a problem, give a clear and concise description of what is the problem. Ex. I'm always frustrated when [...]

Script fails due to error 401, I presume because I have auth enabled and a API key generated.

Describe the solution you'd like. A clear and concise description of what you want to happen.

Check for enabled auth and use the API key when querying the GQL endpoint.

Describe alternatives you've considered. A clear and concise description of any alternative solutions or features you've considered.

No response

Snapshots / Images

No response

David-Maisonave commented 3 months ago

I was able to reproduce this, and created a fix on 0.8.4 version. You can download this version from Axter-Stash->FileMonitor.

It may be a while before I update the version in the CommunityScripts->FileMonitor.

I don't usually update the CommunityScripts with minor changes, unless it's a serious bug.

With the new 0.8.4 version, open the filemonitor_config.py, and look for the apiKey. Populate that field with your ApiKey, and restart the FileMonitor service.

FYI: In my setup, FileMonitor worked when started as a plugin without needing the ApiKey. When started as a service is when it failed.

David-Maisonave commented 3 months ago

I made an additional change which removes the need to populated the API key in the filemonitor_config.py. The new 0.8.5 version will automatically pass the API Key to the service.

I left the apiKey field in the filemonitor_config.py because it still can be useful if user wants to run the script from the command line. Otherwise if it's run from the Stash UI as a service, or if it's run as a plugin, the field does not need to be populated.