You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the velero template there are a LOT of defaults populated via the set list.
One of these is the prefix which is taken from the s3_backup_location using a split on /.
This is coded to only take the first result, so any nested prefix is truncated e.g. 'foo/bar' becomes foo.
This would not be a problem except that I cannot override it by setting it myself in the values; it keeps creating it using the result of the split.
Can we either allow the prefix to be more than one level deep; or provide a way to override, or to switch off, the use of the set so I can do it myself.
I used to be able to do this in the previous version of blueprints v4.32.1 !
If your request is for a new feature, please use the Feature request template.
I don't consider this a feature request at this time as the blueprint should at the very least provide a method to override the default method of specifying the prefix.
[ x] ✋ I have searched the open/closed issues and my issue is not listed.
Try to install velero with a nested prefix (i.e. a prefix containing a /); either via s3_backup_location or values.
Expected behaviour
Either the prefix should include my entire value e.g. foo/bar OR I should be able to override the generated prefix via the values OR have the ability to off the set entirely.
Actual behaviour
My prefix is stripped so I end up with foo instead of foo/bar AND I cannot override it via values.
Terminal Output Screenshot(s)
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
boatmisser
changed the title
Velero: Unable to use a nested prexix, nor override it by setting it myself in values
Velero: Unable to use a nested prefix, nor override it by setting it myself in values
Nov 8, 2023
This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days
Description
In the
velero
template there are a LOT of defaults populated via theset
list.One of these is the
prefix
which is taken from thes3_backup_location
using a split on/
.This is coded to only take the first result, so any nested prefix is truncated e.g. 'foo/bar' becomes
foo
.This would not be a problem except that I cannot override it by setting it myself in the
values
; it keeps creating it using the result of the split.Can we either allow the
prefix
to be more than one level deep; or provide a way to override, or to switch off, the use of theset
so I can do it myself.I used to be able to do this in the previous version of blueprints v4.32.1 !
If your request is for a new feature, please use the
Feature request
template.I don't consider this a feature request at this time as the blueprint should at the very least provide a method to override the default method of specifying the
prefix
.Versions
Module version [Required]: 1.11.0
Terraform version: 1.6.3
Reproduction Code [Required]
velero.yaml
Result is always:
Expect:
Steps to reproduce the behaviour:
Try to install
velero
with a nestedprefix
(i.e. aprefix
containing a/
); either vias3_backup_location
orvalues
.Expected behaviour
Either the
prefix
should include my entire value e.g.foo/bar
OR I should be able to override the generated prefix via thevalues
OR have the ability to off theset
entirely.Actual behaviour
My
prefix
is stripped so I end up withfoo
instead offoo/bar
AND I cannot override it viavalues
.Terminal Output Screenshot(s)
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: