-
Notifications
You must be signed in to change notification settings - Fork 9
AAP-58797: Operator - Implement Chatbot authentication #693
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
base: main
Are you sure you want to change the base?
Conversation
a86344f to
238dd91
Compare
ldjebran
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
238dd91 to
5be99d2
Compare
|
rebased |
5be99d2 to
e39d78f
Compare
|
rebased |
e39d78f to
880b638
Compare
|
Go to bed 😅 |
|
Getting crazy @ldjebran I fixed this operator PR and tested locally. All good, I see the chatbot api key secret and the ENVs, in both wisdom and chatbot containers. Chatbot configuration also OK. Soooo WHY the f*** the tests are failing??? I can't see still see it :( Also tested the wisdom status endpoint and I see chatbot endpoints are OK: |
5926240 to
770affe
Compare
Signed-off-by: romartin <[email protected]>
770affe to
ddf55bd
Compare
Jira Issue: https://issues.redhat.com/browse/AAP-58797
Description
Enabled chatbot authentication.
Testing
Tested operator locally against an AAP instance, in a CRC cluster.
Production deployment