Skip to content

chore: Set datacite secret using new parameter #184

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

Merged
merged 1 commit into from
Apr 18, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions charts/invenio/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ invenio:
password: ""
## @param invenio.datacite.existingSecret Existing secret name for datacite username and password
##
existingSecret: ""
existingSecret: "datacite-secrets"
## @param invenio.datacite.secretKeys.usernameKey Name of key in existing secret to use for username. Only used when `invenio.datacite.existingSecret` is set.
## @param invenio.datacite.secretKeys.passwordKey Name of key in existing secret to use for password. Only used when `invenio.datacite.existingSecret` is set.
##
Expand All @@ -110,7 +110,7 @@ invenio:
existing_secret: false
## @param invenio.datacite.secret_name DEPRECATED: use invenio.datacite.existingSecret instead
##
secret_name: "datacite-secrets"
secret_name: ""
podSecurityContext:
enabled: true
remote_apps:
Expand Down