Plugin Generator throws `ApplicationSet: strict decoding error: unknown field "spec.generators[0].plugin"` about applicationset HOT 4 CLOSED

To be absolutely sure this is not working (at least in my environment), I created a repo from the argoproj-labs/applicationset-hello-plugin template repo here, and it still seems to have returned the same error:

$ kustomize build | kubectl apply -f -
namespace/applicationset-hello-plugin created
configmap/hello-plugin-script-k5g94b88g8 created
configmap/applicationset-hello-plugin created
secret/applicationset-hello-plugin created
secret/applicationset-hello-plugin created
service/applicationset-hello-plugin created
deployment.apps/applicationset-hello-plugin created

$ kubectl apply -f test_applicationset.yaml
Error from server (BadRequest): error when creating "test_applicationset.yaml": ApplicationSet in version "v1alpha1" cannot be handled as a ApplicationSet: strict decoding error: unknown field "spec.generators[0].plugin"

test_applicationset.yaml is the one from the README here:

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: myplugin
spec:
  generators:
    - plugin:
        configMapRef:
          name: applicationset-hello-plugin
  template:
    metadata:
      name: "from-appset-{{hello}}"
    spec:
      project: default
      source:
        repoURL: https://github.com/argoproj/argocd-example-apps.git
        path: .
      destination:
        server: https://kubernetes.default.svc
        namespace: default

Is there something I need to update in the main argocd configmap or anything to make it work? Maybe I just missed a setting 🤔

from applicationset.

Oh no, I just realized I was looking at the v:latest documentation this whole time because it has syntax highlighting and v:stable does not. This feature isn't in stable and I'm running a stable image version 🤦

Let me try latest, because I have a good test environment with k3s where I can just wipe the cluster and try fresh and I want to experiment anyway :)

from applicationset.

oh double no.... how did I not notice the blatant deprecation notice on this repo 🤦

Will reopen in the argocd repo, if this is an issue in stable 2.8.

Minor suggestion to use the GitHub public archive feature though, so it's clear at the top of repo that this is not active. I feel silly for not reading the README here though :)

from applicationset.

For anyone else who may have gotten lost:
It works in v2.8.0-rc7 by setting global.image.tag in values.yaml for your helm install to v2.8.0-rc7 and then applying this CRD. :)

from applicationset.