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

Make PVPatchMaximumDuration timeout configurable #8021

Merged

Conversation

shubham-pampattiwar
Copy link
Collaborator

Thank you for contributing to Velero!

Please add a summary of your change

Does your change fix a particular issue?

Fixes #(issue)

Please indicate you've done the following:

  • Accepted the DCO. Commits without the DCO will delay acceptance.
  • Created a changelog file or added /kind changelog-not-required as a comment on this pull request.
  • Updated the corresponding documentation in site/content/docs/main.

Copy link

codecov bot commented Jul 16, 2024

Codecov Report

Attention: Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 58.82%. Comparing base (35c90f1) to head (fd6c747).
Report is 10 commits behind head on main.

Files Patch % Lines
pkg/cmd/server/server.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8021   +/-   ##
=======================================
  Coverage   58.82%   58.82%           
=======================================
  Files         346      346           
  Lines       28886    28889    +3     
=======================================
+ Hits        16993    16995    +2     
- Misses      10464    10465    +1     
  Partials     1429     1429           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Lyndon-Li
Copy link
Contributor

@shubham-pampattiwar We discussed this today, we suggest to use the existing resource-timeout flag which is almost for the same purpose. We don't need to add a new flag which will make the UX complex.

@shubham-pampattiwar shubham-pampattiwar force-pushed the expose-pv-patch-max-timeout branch from 92388ff to ef6d3ab Compare July 18, 2024 20:34
@shubham-pampattiwar shubham-pampattiwar marked this pull request as ready for review July 18, 2024 20:34
@github-actions github-actions bot requested review from blackpiglet and sseago July 18, 2024 20:35
@shubham-pampattiwar
Copy link
Collaborator Author

@Lyndon-Li makes sense, I have updated the PR, PTAL!

@shubham-pampattiwar shubham-pampattiwar changed the title Expose PVPatchMaximumDuration timeout for custom configuration Make PVPatchMaximumDuration timeout configurable Jul 18, 2024
@shubham-pampattiwar shubham-pampattiwar force-pushed the expose-pv-patch-max-timeout branch from ef6d3ab to 671985c Compare July 18, 2024 20:37
Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com>

remove debug log

Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com>

use resource timeout server arg

Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com>

add changelog

Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com>

remove hardcoded PVPatchMaximumtimeout const usagDe

Signed-off-by: Shubham Pampattiwar <spampatt@redhat.com>
@Lyndon-Li Lyndon-Li merged commit 6e27ed3 into vmware-tanzu:main Jul 22, 2024
66 checks passed
@Lyndon-Li
Copy link
Contributor

@shubham-pampattiwar Please help to make the cherry-pick. Thanks.

@shubham-pampattiwar
Copy link
Collaborator Author

@Lyndon-Li CP: #8035

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

Successfully merging this pull request may close these issues.

Expose PVPatchMaximumDuration timeout for custom configuration
3 participants