shuting

> @chipzoller @realshuting @prateekpandey14, I've added `foreach` for generation block and it's working fine according to me, Now I think it's ready to test, Let me know if you find...

@MdSahil-oss - how does this rule generate multiple resources for **each** container? How I read the following rule is - it generates one configmap for each item defined under `generate.foreach`:...

> ```yaml > generate: > foreach: > - list: "request.object.spec.containers" > kind: ConfigMap > apiVersion: v1 > name: "custom-created-configmap" > namespace: "{{request.object.metadata.namespace}}" > synchronize: false > data: > data: >...

> I have a prototype in mind that requires significant changes but would make autogen a lot simpler/reliable. > > Instead of trying to synthesise rules for higher level controllers...

>If you have a Deployment for example, you take what you have in spec.template and this gives you something very close to a Pod you can evaluate against the policy....

> @realshuting we can support everything as long as we are able to extract something that looks like a pod. Yes, I wonder if we could always extract pod's spec...

> > Yes, I wonder if we could always extract pod's spec with path spec.template.spec 🤔 > > Nope because for cronjobs it's a bit different for example. That's my...

Can we close this? Anything else to be added?

>Could we make it possible to override and turn on the auto-gen feature, even if a resource selector/name/annotation is specified under a match/exclude block - by setting the value of...

@chipzoller - do we need to update docs?