standardize content naming for unnamed content

testdata/contents.yaml

@@ -5,17 +5,17 @@ metadata:
 spec:
   files:
     # hauler can save/redistribute files on disk (be careful! paths are relative)
-    - ref: testdata/contents.yaml
+    - path: testdata/contents.yaml
 
     # TODO: when directories are specified, they will be archived and stored as a file
-#    - ref: testdata/
+#    - path: testdata/
 
     # hauler can also fetch remote content, and will "smartly" identify filenames _when possible_
     #   filename below = "k3s-images.txt"
-    - ref: "https://github.com/k3s-io/k3s/releases/download/v1.22.2%2Bk3s2/k3s-images.txt"
+    - path: "https://github.com/k3s-io/k3s/releases/download/v1.22.2%2Bk3s2/k3s-images.txt"
 
     # when filenames are not appropriate, a name should be specified
-    - ref: https://get.k3s.io?filename=get-k3s.sh
+    - path: https://get.k3s.io?filename=get-k3s.sh
 
 ---
 apiVersion: content.hauler.cattle.io/v1alpha1
@@ -25,16 +25,16 @@ metadata:
 spec:
   images:
     # images can be referenced shorthanded without a tag
-    - ref: hello-world
+    - name: hello-world
 
     # or namespaced with a tag
-    - ref: rancher/cowsay:latest
+    - name: rancher/cowsay:latest
 
     # or by their digest:
-#    - ref: registry@sha256:42043edfae481178f07aa077fa872fcc242e276d302f4ac2026d9d2eb65b955f
+    - name: registry@sha256:42043edfae481178f07aa077fa872fcc242e276d302f4ac2026d9d2eb65b955f
 
     # or fully qualified from any OCI compliant registry registry
-    - ref: ghcr.io/fluxcd/flux-cli:v0.22.0
+    - name: ghcr.io/fluxcd/flux-cli:v0.22.0
 
 ---
 apiVersion: content.hauler.cattle.io/v1alpha1