-
Notifications
You must be signed in to change notification settings - Fork 57
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
kubeobjects: disable hooks #1533
base: main
Are you sure you want to change the base?
kubeobjects: disable hooks #1533
Conversation
c5fd7ec
to
95fbf66
Compare
So far, we don't have the ability to run hooks specified in a recipe. We were wrongly passing these hooks to velero in the capture or recover spec. This commit disables the hooks completely by skipping them. In a later PR, we will add the ability to run the hooks in the recipe natively in Ramen. Signed-off-by: Raghavendra Talur <[email protected]>
95fbf66
to
6e0a45b
Compare
Fixes #1544 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Why passing the hook to velero is wrong? https://github.com/RamenDR/ramen/blob/main/docs/recipe.md does not specify how hooks should run. Maybe start this work by updating the doc to explain the desired behavior? |
@raghavendra-talur the envtest failure seems genuine as it is a hook test is some different namespace. As hooks are disabled here, that test will not pass and needs to be removed or disabled. |
So far, we don't have the ability to run hooks specified in a recipe. We
were wrongly passing these hooks to velero in the capture or recover
spec.
This commit disables the hooks completely by skipping them. In a later
PR, we will add the ability to run the hooks in the recipe natively in
Ramen.