Skip to content

bugfix: fix docker config secret's name used in config #50

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
Jul 11, 2023

Conversation

GeorgianaElena
Copy link
Member

When trying to use the latest changes in 2i2c-org/infrastructure#2699, that deploys this into the staging namespace, I realized that {{ .Release.Name }} expands to staging and not to staging-binderub-service .

Hopefully this fixes it.

@GeorgianaElena GeorgianaElena changed the title Fix docker config secret's name used in config bugfix: fix docker config secret's name used in config Jul 11, 2023
@GeorgianaElena GeorgianaElena merged commit 3f8250e into 2i2c-org:main Jul 11, 2023
consideRatio pushed a commit that referenced this pull request Jul 11, 2023
…fd0278

#50 Merge pull request #50 from GeorgianaElena/fix-secret-name
@GeorgianaElena GeorgianaElena deleted the fix-secret-name branch July 11, 2023 14:49
- name: HELM_RELEASE_NAME
value: {{ .Release.Name }}
- name: HELM_DEPLOYMENT_NAME
value: {{ include "binderhub-service.fullname" . }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah nice catch @GeorgianaElena, perfect!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants