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

Show opa version badge in main, and each release doc #2181

Closed
ritazh opened this issue Jul 20, 2022 · 10 comments
Closed

Show opa version badge in main, and each release doc #2181

ritazh opened this issue Jul 20, 2022 · 10 comments
Assignees
Labels
docs Pure prose good first issue Good for newcomers triaged

Comments

@ritazh
Copy link
Member

ritazh commented Jul 20, 2022

Opa upgrade now comes from framework. Can you try latest commit in master? that is referencing framework that’s using opa v0.35 https://github.com/open-policy-agent/frameworks/pull/167/files#diff-45830b37d8fe6cfa6317672df498ec856ff48ffd48cd2537d18337e6281d6618R14

+1 on showing opa version badge in master, and perhaps for each release doc. thoughts?

Originally posted by @ritazh in #1827 (comment)

@stale
Copy link

stale bot commented Sep 18, 2022

This issue 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 Sep 18, 2022
@ritazh
Copy link
Member Author

ritazh commented Sep 18, 2022

still relevant

@sozercan
Copy link
Member

sozercan commented Jul 18, 2023

#2888 has some additional context too

@ritazh
Copy link
Member Author

ritazh commented Aug 11, 2023

xref: #1827 (comment)

@ritazh
Copy link
Member Author

ritazh commented Aug 11, 2023

Today, you have to go to the last commit for the GK release you are using, from GK go.mod check the framework commit then check framework/constraint's go.mod to see what version of opa that release is using.

@jestadi0795
Copy link

+1 for showing up OPA Version being used with respective Gatekeeper release which can solve below problems.

  • Safe usage of OPA new features like "future.keywords", new builtin functions, metadata etc..
  • Safe Gatekeeper upgrades can be performed without breaking any functionality

Hope this gets addressed soon !!

@salaxander
Copy link
Contributor

Working on getting this into the docs, but here's a map of major versions for the short term:

  • Gatekeeper v3.1.0 -> OPA v0.19.1
  • Gatekeeper v3.2.0 -> OPA v0.19.1
  • Gatekeeper v3.3.0 -> OPA v0.24.0
  • Gatekeeper v3.4.0 -> OPA v0.24.0
  • Gatekeeper v3.4.1 -> OPA v0.24.0
  • Gatekeeper v3.5.0 -> OPA v0.24.0
  • Gatekeeper v3.5.1 -> OPA v0.24.0
  • Gatekeeper v3.5.2 -> OPA v0.24.0
  • Gatekeeper v3.6.0 -> OPA v0.24.0
  • Gatekeeper v3.7.0 -> OPA v0.29.4
  • Gatekeeper v3.7.1 -> OPA v0.29.4
  • Gatekeeper v3.7.2 -> OPA v0.29.4
  • Gatekeeper v3.8.0 -> OPA v0.39.0
  • Gatekeeper v3.8.1 -> OPA v0.39.0
  • Gatekeeper v3.9.0 -> OPA v0.41.0
  • Gatekeeper v3.9.1 -> OPA v0.44.0
  • Gatekeeper v3.9.2 -> OPA v0.44.0
  • Gatekeeper v3.10.0 -> OPA v0.44.0
  • Gatekeeper v3.11.0 -> OPA v0.47.2
  • Gatekeeper v3.11.1 -> OPA v0.47.2
  • Gatekeeper v3.12.0 -> OPA v0.49.2
  • Gatekeeper v3.13.0 -> OPA v0.54.0

@sozercan
Copy link
Member

As part of this issue, can we make sure that this is automated in the future?

@salaxander
Copy link
Contributor

Yeah that's the intent :)

@ritazh
Copy link
Member Author

ritazh commented Oct 9, 2024

fixed via #3537

@ritazh ritazh closed this as completed Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Pure prose good first issue Good for newcomers triaged
Projects
Status: ✅ Done
Development

No branches or pull requests

5 participants