Skip to content
This repository has been archived by the owner on Jan 23, 2025. It is now read-only.

Our objective is to align the titles and logic with the commercial version. #1382

Merged
merged 3 commits into from
Jul 27, 2023

Conversation

mjshastha
Copy link
Contributor

@mjshastha mjshastha commented Jul 10, 2023

Our objective is to align the titles and logic with the commercial version.

@mjshastha mjshastha requested review from giorod3 and simar7 as code owners July 10, 2023 09:03
@CLAassistant
Copy link

CLAassistant commented Jul 10, 2023

CLA assistant check
All committers have signed the CLA.

@simar7 simar7 requested a review from chen-keinan July 10, 2023 20:06
@simar7
Copy link
Member

simar7 commented Jul 10, 2023

hi @chen-keinan could you take a look?

@dheerajkadri
Copy link
Contributor

Please cross check if the title updates are in sync with the AVD_DOCS

@mjshastha
Copy link
Contributor Author

Please cross check if the title updates are in sync with the AVD_DOCS

verified

@mjshastha mjshastha force-pushed the updating_rego_titles branch from 721b9eb to 6126b63 Compare July 17, 2023 08:52

changeVerbs := ["update", "create", "*"]
changeVerbs := ["create", "update", "patch", "delete", "deletecollection", "impersonate", "*"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wondering why we are using asterisk (*) here - wildcard character that matches any string. We have added more verbs now. Do we still need * ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Certainly! We have expanded the list of verbs and included the wildcard "*" value in order to align the oss with the commercial.

Copy link
Contributor

@dheerajkadri dheerajkadri Jul 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we are using the wildcard (*), then there is no need to define verbs explicitly, since the asterisk( * ) will match any verb. Using the wildcard character could result in the policy generating false positives. Additionally, using the wildcard character could make the policy less efficient, as it will have to check for rules that allow a wider range of verbs.

Can you check if we really need this wildcard character ? this is used in many checks

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I concur that including a wildcard () in the verbs list negates the need to define verbs explicitly, as the asterisk () will match any verb. The asterisk (*) was already present in the verbs list, and I introduced additional verbs to ensure alignment between the oss and commercial.

@chen-keinan
Copy link
Contributor

in general lgtm , see failing tests

@mjshastha mjshastha force-pushed the updating_rego_titles branch from 6126b63 to 89d51e0 Compare July 27, 2023 03:56
@mjshastha
Copy link
Contributor Author

mjshastha commented Jul 27, 2023

@chen-keinan I have addressed the issues with the failing tests. Could you approve and run the workflows?

@chen-keinan
Copy link
Contributor

@mjshastha could you please rebase your branch with upstream

@mjshastha mjshastha force-pushed the updating_rego_titles branch from 89d51e0 to 6f4d882 Compare July 27, 2023 09:10
@simar7 simar7 merged commit a9ded81 into aquasecurity:master Jul 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants