🐛 Spacing is incorrect in docs/migration/crds/workspaces_patch_a.yaml.

[justinb-shipt]

Operator Version, Kind and Kubernetes Version

• Operator version: v1 to v2 migration
• Kind: Workspace | Module
• Kubernetes version: 1.26, 1.27

YAML Manifest File

N/A

Output Log

N/A

Output of relevant kubectl commands

❯ kubectl diff -f workspaces_patch_a.yaml error: error parsing workspaces_patch_a.yaml: error converting YAML to JSON: yaml: line 330: did not find expected key

Steps To Reproduce

https://developer.hashicorp.com/terraform/cloud-docs/integrations/kubernetes/ops-v2-migration

Expected Behavior

What should have happened?

Should have returned a successful diff.

Actual Behavior

What actually happened?

error: error parsing workspaces_patch_a.yaml: error converting YAML to JSON: yaml: line 330: did not find expected key

Additional Context

Add any other context about the problem here.

Not exactly a bug with the Operator, but a bug within the files provided for migration. I added 2 additional spaces for the entire v1alpha2 section and was able to get a successful diff. I have not tested the b patch yet.

❯ kubectl diff -f workspaces_patch_a.yaml
diff -u -N /var/folders/r1/ddmpvl596pxgl9116g4b67180000gq/T/LIVE-2625289397/apiextensions.k8s.io.v1.CustomResourceDefinition..workspaces.app.terraform.io /var/folders/r1/ddmpvl596pxgl9116g4b67180000gq/T/MERGED-2644053759/apiextensions.k8s.io.v1.CustomResourceDefinition..workspaces.app.terraform.io
--- /var/folders/r1/ddmpvl596pxgl9116g4b67180000gq/T/LIVE-2625289397/apiextensions.k8s.io.v1.CustomResourceDefinition..workspaces.app.terraform.io  2024-02-10 13:50:33
+++ /var/folders/r1/ddmpvl596pxgl9116g4b67180000gq/T/MERGED-2644053759/apiextensions.k8s.io.v1.CustomResourceDefinition..workspaces.app.terraform.io    2024-02-10 13:50:33
@@ -2,11 +2,11 @@
 kind: CustomResourceDefinition
 metadata:
   annotations:
-    controller-gen.kubebuilder.io/version: v0.8.0
+    controller-gen.kubebuilder.io/version: v0.11.3
<snip>

References

Community Note

• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.