Skip to content
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.

Update velero to 1.5.2 #1131

Merged
merged 2 commits into from
Nov 2, 2020
Merged

Update velero to 1.5.2 #1131

merged 2 commits into from
Nov 2, 2020

Conversation

ipochi
Copy link
Member

@ipochi ipochi commented Oct 28, 2020

Release notes: Since this PR also updates the CRD, they need to be manually updated first.

Step before updating the component:

kubectl apply -f https://github.com/vmware-tanzu/helm-charts/tree/main/charts/velero/crds

if len(providers) == 0 {
return nil, fmt.Errorf("no providers configured")
if len(providers) != 1 {
return nil, fmt.Errorf("cannot have more than one provider configured, got: %d", len(providers))
Copy link
Member

Choose a reason for hiding this comment

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

"cannot have more than one provider configured, got: 0" doesn't make sense.

Copy link
Member Author

Choose a reason for hiding this comment

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

@invidian I have removed one conditional statement and revised the error message. If you think having two conditionals make sense for a better error message then I have no problems.

@ipochi ipochi force-pushed the imran/update-velero-to-1.5.2 branch from 0249b8e to f0f5d9b Compare November 2, 2020 08:34
Signed-off-by: Imran Pochi <imran@kinvolk.io>
Signed-off-by: Imran Pochi <imran@kinvolk.io>
@ipochi ipochi force-pushed the imran/update-velero-to-1.5.2 branch from f0f5d9b to bf9658d Compare November 2, 2020 10:17
@ipochi ipochi merged commit d804f25 into master Nov 2, 2020
@ipochi ipochi deleted the imran/update-velero-to-1.5.2 branch November 2, 2020 11:05
@invidian invidian mentioned this pull request Nov 2, 2020
@invidian invidian mentioned this pull request Dec 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants