Michael Crenshaw

I like this idea a lot. One way would be to write a REST generator and then parameterize the heck out of it. But that seems fragile. Argo Workflows has...

Makes sense! I think we could make a JSON body part of the contract and then pass a generic `object` as one of the fields for parameters. That should leave...

@povils I think we have enough of a rough sketch for a design that a proof of concept could be built. Unfortunately I won't have time in the foreseeable future...

I think you'd just define a new `HTTPGenerator` which accepts `url` as a parameter. Then accept as a response any JSON list of objects. The key/value pairs in the objects...

If we limit it to `localhost` for sidecar plugins at first, I think we can skip auth. But yes, eventually we'd need to be able to parameterize it with secret...

Fixed via https://github.com/argoproj/argo-cd/pull/8998

Seems like a good feature! Would you be interested in contributing the filter? I think you could reuse the existing client logic to detect 404s as a positive rather than...

@mmerrill3 can you take a look?

@oleg-glushak sounds like I need to write some more tests...

@romuduck wouldn't a file generator with something like `../**/config.yaml` be the same thing as a file x directory matrix generator?