Skip to content
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

Should k8s-binder-k8s-hub/binderhub-chart-config-old.yaml be kept or deleted? #1520

Open
manics opened this issue Aug 2, 2022 · 1 comment

Comments

@manics
Copy link
Member

manics commented Aug 2, 2022

k8s-binder-k8s-hub/binderhub-chart-config-old.yaml says it should be deleted:

# (DELETE ME)
# this file should be removed immediately after merging PR #1472

However it's referenced in the CI workflows:
old_config="../testing/k8s-binder-k8s-hub/binderhub-chart-config-old.yaml"
if [ -f "$old_config" ]; then
echo "using old config"
else
old_config="../testing/k8s-binder-k8s-hub/binderhub-chart-config.yaml"
fi

old_config="../testing/k8s-binder-k8s-hub/binderhub-chart-config-old.yaml"
if [ -f "$old_config" ]; then
echo "using old config"
else
old_config="../testing/k8s-binder-k8s-hub/binderhub-chart-config.yaml"
fi

Should it be kept and the comment removed, or should the file and all references to it be deleted?

@consideRatio
Copy link
Member

consideRatio commented Oct 8, 2022

I recognize the need for having two sets of helm chart configuration because the CI system tests against an old version and then upgrades to a new version etc. I presume this is about that, and that we can now remove everything related to it.

@minrk you added the DELETE ME note, do you agree on deleting the file and all logic referencing it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants