Allow existing secrets for passwords #170
No reviewers
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#170
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "allow-secrets-for-password"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Allow admin user and password to be configured via existing secrets
Allow LDAP bindDn and bindPassword to be configured via existing secrets
Update Readme
Fixes: #169
Tested on my cluster
Tested on my cluster too.
Seems working fine!
Thank you!
@ -309,0 +341,4 @@
```yaml
gitea:
admin:
Whouldn't it be
gitea.ldap.existingSecret
instead ofgitea.admin.existingSecret
for the ldap configuration?good catch!
b62cde2aab
to7f2d439745
7f2d439745
to084cd19123
Fixed another bug and updated the branch with the current master
@luhahn shouldn't you approve this also?
You can't approve your own PRs :)
This pr is again a breaking change for existing users ? see #179