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

revert!: remove legacy engines from the flow #157

Merged
merged 1 commit into from
Mar 21, 2024

Conversation

Abhinandan-Purkait
Copy link
Member

DISABLED cSTOR and JIVA stem commands as these engines are to be made legacy and deprecated.

Changes

  • Removed cstor related operations.
  • Removed blockdevice related operations.
  • Removed cstor and jiva upgrade functionality.
  • Removed cstor and jiva test data.
  • Removed tests around cstor and jiva.

@codecov-commenter
Copy link

Codecov Report

Attention: Patch coverage is 15.38462% with 11 lines in your changes are missing coverage. Please review.

Project coverage is 56.35%. Comparing base (2e58733) to head (b49ef67).

Files Patch % Lines
pkg/storage/storage.go 0.00% 7 Missing ⚠️
pkg/persistentvolumeclaim/persistentvolumeclaim.go 0.00% 3 Missing ⚠️
pkg/storage/lvmlocalpv.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##           develop     #157       +/-   ##
============================================
- Coverage    69.92%   56.35%   -13.58%     
============================================
  Files           26       15       -11     
  Lines         2148      834     -1314     
============================================
- Hits          1502      470     -1032     
+ Misses         630      362      -268     
+ Partials        16        2       -14     

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

Copy link
Member

@niladrih niladrih left a comment

Choose a reason for hiding this comment

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

Left one comment

go.mod Outdated Show resolved Hide resolved
@niladrih
Copy link
Member

Could you take a look at the failing CI?

@Abhinandan-Purkait
Copy link
Member Author

Could you take a look at the failing CI?

I just updated all the github workflows. It should work now.

@Abhinandan-Purkait Abhinandan-Purkait force-pushed the deprecate_legacy branch 2 times, most recently from e8ab473 to b4944ea Compare March 13, 2024 12:11
@Abhinandan-Purkait Abhinandan-Purkait changed the title chore: remove legacy engines from the flow revert!: remove legacy engines from the flow Mar 21, 2024
Signed-off-by: Abhinandan Purkait <purkaitabhinandan@gmail.com>
Copy link
Member

@niladrih niladrih left a comment

Choose a reason for hiding this comment

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

LGTM

@Abhinandan-Purkait Abhinandan-Purkait merged commit 9d8d2fd into develop Mar 21, 2024
9 checks passed
@Abhinandan-Purkait Abhinandan-Purkait deleted the deprecate_legacy branch March 21, 2024 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants