From 640182df108cbb8c9e103835d613e91da629a0d3 Mon Sep 17 00:00:00 2001
From: Dusty Mabe <dusty@dustymabe.com>
Date: Fri, 22 May 2020 18:14:52 -0400
Subject: [PATCH] Jenkinsfile: attach nested virtualization license to GCP
 images

This will allow for launched instances to have access to /dev/kvm
by default. I am not aware of any known drawbacks to doing this as
I've been informed by GCP folks that if there is an environment that
doesn't have nested virt support or if there is a policy that disallows
it the instance simply won't have access to /dev/kvm. No other errors
would be presented to the user (like not being able to launch an
instance).
---
 Jenkinsfile | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Jenkinsfile b/Jenkinsfile
index 4f5d1593e..f02632dc4 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -448,6 +448,7 @@ lock(resource: "build-${params.STREAM}") {
                         --deprecated \
                         --family fedora-coreos-${params.STREAM} \
                         --license fedora-coreos-${params.STREAM} \
+                        --license "https://compute.googleapis.com/compute/v1/projects/vm-options/global/licenses/enable-vmx" \
                         --project=\${gcp_project} \
                         --bucket gs://${gcp_gs_bucket}/image-import \
                         --json \${GCP_IMAGE_UPLOAD_CONFIG} \