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

Cleanup AutoYaST issue and profile handling #1091

Merged
merged 32 commits into from May 29, 2020
Merged

Conversation

schubi2
Copy link
Member

@schubi2 schubi2 commented May 8, 2020

Problem

Each module (storage, firewall,network) has his own AutoYaST Issue and profile handling which is incompatible and doubles the code.
bsc#1171335

Solution

Bring base classes to yast2 package and cleanup the code of the other packages which will use
these common base classes:
yast/yast-yast2#1050
yast/yast-yast2#1055

Testing

  • Adding test cases for showing the issues
  • Tested manually.

Bildschirmfoto_2020-05-12_14-11-12

@schubi2 schubi2 changed the title WIO: Cleanup AutoYaST issue handling WIP: Cleanup AutoYaST issue handling May 8, 2020
@coveralls
Copy link

coveralls commented May 26, 2020

Coverage Status

Coverage increased (+0.005%) to 97.644% when pulling a53df19 on master-issue-report into 783913f on master.

@schubi2 schubi2 changed the title WIP: Cleanup AutoYaST issue handling Cleanup AutoYaST issue and profile handling May 27, 2020

module Y2Storage
module Installation
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should not move this code to a different module/namespace. IMHO, it is OK that specific storage-ng issues live under the Y2Storage::AutoinstIssues namespace.

@schubi2 schubi2 merged commit af94428 into master May 29, 2020
@schubi2 schubi2 deleted the master-issue-report branch May 29, 2020 13:09
@yast-bot
Copy link

✔️ Public Jenkins job #309 successfully finished
✔️ Created OBS submit request #810217

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.

None yet

4 participants