Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ Enhancement ] Allow secure redis to be supported #146

Open
gwright99 opened this issue Sep 12, 2024 · 1 comment
Open

[ Enhancement ] Allow secure redis to be supported #146

gwright99 opened this issue Sep 12, 2024 · 1 comment

Comments

@gwright99
Copy link
Collaborator

Current as of Release 1.3.1, the Redis URL used by Seqera Platform / Connect is controlled by the following 2 locals:

  • tower_redis_url
  • tower_connect_redis_url

Investigate the feasibility of exposing a mechanism to change the redis:// prefix to rediss://.

@gwright99
Copy link
Collaborator Author

gwright99 commented Sep 12, 2024

TO DO:

  • Verify configured redis URLs are not secured
    • Ensure TOWER_REDIS_URL is not prefixed with rediss:// if Seqera Platform is v24.1.0, v24.1.1, v24.1.2, or v24.1.3
    • Ensure CONNECT_REDIS_ADDRESS is not prefixed with rediss:// if Connect is v0.7.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant