Alright...I can't find where environment variables are declared for Galaxy.
We're trying to migrate our Apollo services and I cannot make the environment variable change for the life of me. I thought it was in /etc/supervisor/conf.d/<files>
but...evidently it isn't picking up. Even after restart.
Is there another place that environment variables can get declared? Something perhaps that I am missing? At least obvious ones.
<we don't use ansible atm, we are currently old school/bare metal>
print
statements if you're struggling to figure out where it gets stuck in authentication. The last time I had my bind credentials wrong and it took a bit to figure out that that's what was happening.
Add OIDC integration with Azure active directory and restart the Galaxy server.
/opt/galaxy/server/lib/galaxy/jobs/handler.py:360: SAWarning: Coercing Subquery object into a select() for use in IN(); please pass a select() construct explicitly
The last part was like this: WARNING: Discarding https://wheels.galaxyproject.org/simple/futures/futures-3.1.1.tar.gz (from https://wheels.galaxyproject.org/simple/futures/). Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.\nERROR: Could not find a version that satisfies the requirement futures==3.1.1 (from versions: 0.2.python3, 0.1, 0.2, 1.0, 2.0, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.1.0, 3.1.1)\nERROR: No matching distribution found for futures==3.1.1\n"}
PLAY RECAP **
vm : ok=53 changed=0 unreachable=0 failed=1 skipped=33 rescued=0 ignored=0