-
Notifications
You must be signed in to change notification settings - Fork 13
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
feat(auth): allow optional basic authentication (backport #95) #96
Conversation
@tthvo CI is failing for this one. Only the backport strangely. It seems to be upgrade related, but I'm having trouble pinpointing the cause in the logs. If it is upgrade related, it could be something similar to #82 (comment). |
Ahh hmm, I remember handling that null case in...36ff259 (in #95). I am not seeing
Might just be |
Ahh hahaha oh my. I figured it was because there is a mismatched between
This patch will make the test pass: diff --git a/charts/cryostat/Chart.yaml b/charts/cryostat/Chart.yaml
index 49a8052..0a4c97a 100644
--- a/charts/cryostat/Chart.yaml
+++ b/charts/cryostat/Chart.yaml
@@ -8,7 +8,7 @@ version: "0.4.0-dev"
kubeVersion: ">= 1.19.0-0"
-appVersion: "2.4.0-dev"
+appVersion: "2.5.0-dev"
home: "https://cryostat.io" |
I guess we should update the tags of images in |
Ah, that explains it! I think we need to add some steps to do this for the operator and Helm Chart when branching for release. |
Sounds good! I might have missed that when documenting these steps haha^^ |
@Mergifyio rebase |
❌ Unable to rebase: user
|
@Mergifyio rebase |
❌ Base branch update has failedGit reported the following error:
|
* feat(values): add authentication value parameters * feat(auth): implement basic authentication * fix(values): handle nullable cases * docs(readme): update to mention unset auth case (cherry picked from commit e6be8ea)
0f5a9c9
to
fbde6b6
Compare
Finally got it fixed! |
This is an automatic backport of pull request #95 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com