List applying policies in Parallel .status.policies

[creydr]

As the Eventing Authorization feature track describes, target resources of EventPolicies, will reflect in their status, which EventPolicy is applied to them.

For example:

apiVersion: flows.knative.dev/v1
kind: Parallel
metadata:
  name: my-parallel
spec:
  ...
status:
  ...
  policies:
    - name: event-policy
      apiVersion: v1alpha1
    - name: another-event-policy
      apiVersion: v1alpha1

  conditions:
    - type: Ready
      status: "True"
    - type: EventPoliciesReady
      status: "True"

As the Parallel should support EventPolicies, wee need to do the following:

• Update the Parallel reconciler to show applying policies in the Parallel .status.policies and set the Parallel EventPoliciesReady condition. Also watch EventPolicies for changes.
• Set EventPoliciesReady condition to true, in case no policy applies, and set message according to the default-authorization-mode (e.g. Default authorization mode is 'allow-all'). Check the Default Authorization Mode section in the feature track for additional information.

Hint:

• Adding AppliedEventPoliciesStatus to the Parallel is done in Add AppliedEventPoliciesStatus type #7975

Prerequisites:

• Add Library to support on AuthZ #7985
• Add AppliedEventPoliciesStatus type #7975

Additional hints for new contributors before starting with this issue:

1. When the issue has the Draft status, the issue is subject to change and thus should not be started to be worked on
2. Make sure you've read and understood the CONTRIBUTING.md guidelines
3. Make sure you're able to run Knative Eventing locally and run at least the unit tests.
4. Feel free to raise any questions you have either directly here in the issue, in the #knative-eventing Slack channel or join the Eventing Workgroup Meeting
5. When you feel comfortable with this issue, feel free to assign it to you (e.g. by commenting /assign). Please be aware that we might unassign you, if we don't see any progress from your side to give other contributors also a chance to work on this issue.

[varshith257]

/assign

[creydr]

Hey @varshith257,
This issue is ready to be worked on. You can also check on #8014, how we solved this for the Channel (particularly on b7ff773 and 7891138).
Please let us know if you have any questions :)

[varshith257]

Thanks! Will fix it soon

…

On Mon, 24 Jun, 2024, 8:29 pm Christoph Stäbler, ***@***.***> wrote: Hey @varshith257 <https://github.com/varshith257>, This issue is ready to be worked on. You can also check on #8014 <#8014>, how we solved this for the Channel (particularly on b7ff773 <b7ff773> and 7891138 <7891138> ). Please let us know if you have any questions :) — Reply to this email directly, view it on GitHub <#7979 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4BF3HBGFJMH3BTCKKYRSOLZJAX6PAVCNFSM6AAAAABJB2L2CGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWG44DMMRVGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[creydr]

Hello @varshith257 ,
Any updates on this?
As this issue in in iteration 2 which ends next week (July 6th), please let us know if you'll be able to finish it till then (please also count some time for review cycles).
If you don't find time for it, please unassign yourself, so that another contributor could pick this up.

[varshith257]

@creydr Yes I will complete it soon and raise PR by tommorow. I have exams so hadn't done any progress on this. Sorry for it

[creydr]

Hey @varshith257,
thanks for the update. Good luck with your exams.
I only wanted to make sure that we're aligned on the timeline

[rahulii]

hey @varshith257 since this is due end of this week and we are running short of time, would you mind if I assign the issue to myself?
You can pick other issues once your exams are over ?

[varshith257]

@rahulii Working on it. Will submit a PR soon abiding timeline

[creydr]

@rahulii: As we didn't see any progress on this, I think you can take this over if you want

[rahulii]

/assign

[rahulii]

/unassign @varshith257