Merge pull request #6 from yaacov/update-forklift-crd-add-luks-dectyp…

…tion-keys

Update forklift crds, add LUKs

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kubev2v/types",
-  "version": "0.0.15",
+  "version": "0.0.16",
   "description": "Typescript interfaces and types for forklift-console-plugin",
   "license": "Apache-2.0",
   "private": false,
@@ -29,6 +29,7 @@
     "npm": "^10.5.2",
     "prettier": "^3.2.5",
     "rollup": "^4.14.1",
-    "rollup-plugin-dts": "^6.1.0"
+    "rollup-plugin-dts": "^6.1.0",
+    "crdtoapi": "^0.0.17"
   }
 }

src/generated/forklift/crds/forklift.konveyor.io_migrations.yaml

@@ -230,6 +230,10 @@ spec:
                       - phase
                       - reasons
                       type: object
+                    firmware:
+                      description: The firmware type detected from the OVF file produced
+                        by virt-v2v.
+                      type: string
                     hooks:
                       description: Enable hooks.
                       items:
@@ -286,6 +290,44 @@ spec:
                     id:
                       description: 'The object ID. vsphere: The managed object ID.'
                       type: string
+                    luks:
+                      description: Disk decryption LUKS keys
+                      properties:
+                        apiVersion:
+                          description: API version of the referent.
+                          type: string
+                        fieldPath:
+                          description: 'If referring to a piece of an object instead
+                            of an entire object, this string should contain a valid
+                            JSON/Go field access statement, such as desiredState.manifest.containers[2].
+                            For example, if the object reference is to a container
+                            within a pod, this would take on a value like: "spec.containers{name}"
+                            (where "name" refers to the name of the container that
+                            triggered the event) or if no container name is specified
+                            "spec.containers[2]" (container with index 2 in this pod).
+                            This syntax is chosen only to have some well-defined way
+                            of referencing a part of an object. TODO: this design
+                            is not final and this field is subject to change in the
+                            future.'
+                          type: string
+                        kind:
+                          description: 'Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
+                          type: string
+                        name:
+                          description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
+                          type: string
+                        namespace:
+                          description: 'Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
+                          type: string
+                        resourceVersion:
+                          description: 'Specific resourceVersion to which this reference
+                            is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
+                          type: string
+                        uid:
+                          description: 'UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
+                          type: string
+                      type: object
+                      x-kubernetes-map-type: atomic
                     name:
                       description: 'An object Name. vsphere: A qualified name.'
                       type: string