-
Notifications
You must be signed in to change notification settings - Fork 170
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
Include template for Redis for OAuth flow (Openshift) #300
Comments
APIcast is indeed missing password support in redis. Did you try to set the password to empty by using |
I've used this modified apicast template to deploy Redis: https://gist.github.com/mayorova/9825ebea7885335c5540c027023474c8 |
It's not an APIcast problem right, but we have a dependency on Redis so I think it makes sense we provide a template to make that work in our deployment option on OpenShift. I just wanted to share how I made that work along with the issue itself. So let me reword the issue itself so it seems more appropriate here. I did remove the password but the template sets the |
When importing the template you can set params otherwise they are generated. If you'd set REDIS_PASSWORD as a param all that should be set to empty password and possibly work. Anyway, we should add password support. Probably with unifying the configuration into an url: |
The OAuth flow is deprecated. Closing. |
Solution
Use the redis template from Origin upstream
Unfortunately this won't work "as is" for APIcast deployed on OpenShift. So the following changes need to be made.
Either an ImageStream needs to be created or directly editing the config for Redis to include the URL of the registry where the image is hosted. Without this change in the default template the deployment config cannot pull the image.
Also the default template includes setting a password to access the Redis instance.
ENV
and execute all Redis actions with the password or remove the password completely from the template as I have done in my templateWe should cover in more detail the documentation of the specifically setting this up in OpenShift as the OAuth flow is a bit trickier to set up here than native deployment for example.
The text was updated successfully, but these errors were encountered: