Enabling VO-agnostic FTS proxy production #224
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #220
Tagging @ericvaandering as CMS might be impacted directly.
Changes
"none"
option invalues.yaml
, and if so does not declareRUCIO_VO
andRUCIO_FTS_VOMS
.vo
andvoms
to"none"
.Tests
By running
helm template . --kube-version 1.31 --debug --values values.yaml --show-only templates/renew-fts-cronjob.yaml
We get:
In which are correctly missing
RUCIO_VO
andRUCIO_FTS_VOMS
.Follow-up question
Should we avoid creating also
RUCIO_FTS_VO/VOMS_{{ $key }}
?