Skip to content
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

chore: Bump GATOR_VERSION to 1.17.0 from 1.16.3 #586

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

julianKatz
Copy link
Contributor

In the 1.17.0 version of gator (which I've been using on my machine), the --experimental-enable-k8s-native-validation flag has been renamed to --enable-k8s-native-validation. This was preventing me from using the make verify-gator target.

This PR fixes updates the GATOR_VERSION and changes the flag.

In the 1.17.0 version of gator (which I've been using on my machine),
the `--experimental-enable-k8s-native-validation` flag has been renamed
to `--enable-k8s-native-validation`.  This was preventing me from using
the `make verify-gator` target.

This PR fixes updates the GATOR_VERSION and changes the flag.

Signed-off-by: juliankatz <[email protected]>
@julianKatz julianKatz requested a review from a team as a code owner August 27, 2024 19:53
@apeabody
Copy link
Contributor

@julianKatz - Probably want to bump

gatekeeper: [ "3.15.1", "3.16.3" ]
to match?

@sozercan
Copy link
Member

@apeabody correct, we'll need to support both --experimental and non-experimental flags since we support 2 versions

@@ -50,17 +50,17 @@ test-integration:
.PHONY: verify-gator
verify-gator:
ifeq ($(POLICY_ENGINE), rego)
gator verify ./... --experimental-enable-k8s-native-validation=false
gator verify ./... --enable-k8s-native-validation=false
Copy link
Contributor

Choose a reason for hiding this comment

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

We need a conditional check here for GATOR_VERSION, for < 3.17 use experimental flag, for >= 3.17 use updated flag.

Copy link

stale bot commented Oct 28, 2024

This issue/PR has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 28, 2024
@JaydipGabani
Copy link
Contributor

@julianKatz Are you still working on this?

@stale stale bot removed the stale label Oct 28, 2024
@sozercan
Copy link
Member

sozercan commented Dec 4, 2024

if we wait until 3.18 is cut, we should be good with this PR after updating version to 3.18

@ritazh
Copy link
Member

ritazh commented Dec 14, 2024

@julianKatz - Probably want to bump

gatekeeper: [ "3.15.1", "3.16.3" ]

to match?

@julianKatz This PR is really close! can you pls update this to 3.17.1, 3.18.0?

@apeabody apeabody force-pushed the update-gator-version branch from 8f73019 to 684a719 Compare December 19, 2024 23:14
Signed-off-by: Andrew Peabody <[email protected]>
@apeabody apeabody force-pushed the update-gator-version branch from 684a719 to 6ab6bca Compare December 19, 2024 23:20
@apeabody
Copy link
Contributor

@julianKatz - Probably want to bump

gatekeeper: [ "3.15.1", "3.16.3" ]

to match?

@julianKatz This PR is really close! can you pls update this to 3.17.1, 3.18.0?

Hi @ritazh - Can you please check if this is now ready?

Copy link
Member

@ritazh ritazh left a comment

Choose a reason for hiding this comment

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

LGTM

@ritazh ritazh requested a review from JaydipGabani December 20, 2024 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants