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
Fixes #26047 - Add check for puppet in cvv export. #632
Conversation
Issues: #26047 |
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.
Seems pretty good (I didn't test it, but your tests look good also). This almost seems redundant, but I can see that a CV that doesn't contain any puppet repos can still have puppet modules published in a CVV. I just have a nitpick about the code style.
@akofink updated and addressed your comments. Confirmed tests still work:
|
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.
Very nice. Thanks @chris1984 - ACK from me! I'd like another reviewer that's been working on this import/export work to review as well.
@ehelms care to review when you get a moment? |
This PR adds a check to export, to check and see if a cv version contains puppet modules and give the user a friendly error instead of having
tar
complain with something that is confusing.I also re-factored the export checks into a method in the helper file to clean up the code within the content_view_version file to allow for more readability and flexibility for adding more checks etc that come up over time.