-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update rego title in OSS defsec Part2 #1386
Merged
simar7
merged 4 commits into
aquasecurity:master
from
mjshastha:MS_SLK-69409-new_rego_additions
Jul 28, 2023
Merged
Update rego title in OSS defsec Part2 #1386
simar7
merged 4 commits into
aquasecurity:master
from
mjshastha:MS_SLK-69409-new_rego_additions
Jul 28, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mjshastha
force-pushed
the
MS_SLK-69409-new_rego_additions
branch
from
July 14, 2023 07:11
22d8c10
to
58ccd85
Compare
@chen-keinan PTAL after you are back, thanks. |
mjshastha
force-pushed
the
MS_SLK-69409-new_rego_additions
branch
from
July 17, 2023 09:11
58ccd85
to
c5ae09c
Compare
dheerajkadri
approved these changes
Jul 17, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!!
mjshastha
force-pushed
the
MS_SLK-69409-new_rego_additions
branch
from
July 17, 2023 09:36
c5ae09c
to
2c6c5a8
Compare
lgtm |
chen-keinan
previously approved these changes
Jul 26, 2023
mjshastha
force-pushed
the
MS_SLK-69409-new_rego_additions
branch
from
July 27, 2023 09:28
2c6c5a8
to
b1e1569
Compare
Looks like tests are failing and there's a merge conflict with upstream after the first PR was merged. |
…ently part of the commercial but not included in the oss. Additionally, there are certain checks in the oss where two checks are combined into a single check. However, in the commercial, these checks are treated as two separate checks. Therefore, we will be splitting the combined checks from the oss into two distinct checks to align with the commercial implementation.
simar7
force-pushed
the
MS_SLK-69409-new_rego_additions
branch
from
July 28, 2023 17:05
b1e1569
to
b818199
Compare
simar7
approved these changes
Jul 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
we introduced three new rego checks to the oss. These checks are currently part of the commercial but not included in the oss.
Additionally, there are certain checks in the oss where two checks are combined into a single check. However, in the commercial, these checks are treated as two separate checks. Therefore, we will be splitting the combined checks from the oss into two distinct checks to align with the commercial implementation.
Resolves: SLK-69409