-
Notifications
You must be signed in to change notification settings - Fork 519
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
Add the ability to output vmdk via qemu-img #1289
Conversation
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.
🍔
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, just one small concern.
This change allows users to edit the metadata in a variant's cargo.toml to output a vmdk through buildsys via qemu-img.
Double quotes were added to several places in rpm2img to further prevent unwanted globbing and word splitting (SC2086).
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.
🎖️
Issue number:
N/A
Description of changes:
This change allows users to edit the metadata in a variant's cargo.toml to output an OVA compatible vmdk through buildsys via qemu-img.
Double quotes were also added to several places in rpm2img to prevent unwanted globbing and word splitting (SC2086).
Testing done:
Built aws-k8s-1.18 variant with no toml changes and received the standard img.lz4 output.
Built aws-k8s-1.18 variant with
image-format = "vmdk"
added to the toml and received stream-optimized vmdk output for bottlerocket-aws-k8s-1.18-aarch64 and bottlerocket-aws-k8s-1.18-aarch64-data.Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.