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(opa): Update container image to 1.0.0 ahead of Stackable Release 25.3.0 #969

Open
15 tasks done
Tracked by #964
sbernauer opened this issue Jan 13, 2025 · 4 comments
Open
15 tasks done
Tracked by #964
Assignees
Labels
release-note/action-required Denotes a PR that introduces potentially breaking changes that require user action. scheduled-for/25.3.0 status/blocked

Comments

@sbernauer
Copy link
Member

sbernauer commented Jan 13, 2025

Part of #964.

  • Add: 1.0.0
  • Remove: 0.67.1 edit: Remove 0.66.0

Tip

Please add the scheduled-for/2025-03 label, and add to the Stackable Engineering project.

Update tasks

Preview Give feedback

Tip

Delete any items that do not apply so that all applicable items can be checked.
For example, if you add release notes to the documentation repository, you do not need the latter two criteria.

This list should be completed by the assignee(s), once respective PRs have been merged. Once all items have been checked, the issue can be moved into Development: Done.

Acceptance

Preview Give feedback
Testing instructions
# See the latest version at https://pypi.org/project/image-tools-stackabletech/
pip install image-tools-stackabletech==0.0.13

bake --product opa=x.y.z # where x.y.z is the new version added in this PR

kind load docker-image docker.stackable.tech/stackable/opa:x.y.z-stackable0.0.0-dev

# Change directory into the opa-operator repository and update the
# product version in tests/test-definition.yaml
./scripts/run-tests --test-suite smoke-latest # or similar

Please consider updating this template if these instructions are wrong, or
could be made clearer.

@Maleware
Copy link
Contributor

Deployed end-to-end-security demo. Worked without any problems.

@Maleware
Copy link
Contributor

Maleware commented Jan 24, 2025

Release Notes snipped:

Changes to Rego-Rules:

  1. BREAKINGUsing if for all rule definitions and contains for multi-value rules is now mandatory, not just when using the rego.v1 import.
  2. Other new keywords (every, in) are available without any imports.
  3. Previously requirements that were only run in "strict mode" (like opa check --strict) are now the default. Duplicate imports and imports which shadow each other are no longer allowed.

@Maleware Maleware moved this from Development: In Progress to Development: Waiting for Review in Stackable Engineering Jan 24, 2025
@Maleware Maleware moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Jan 24, 2025
@sbernauer sbernauer moved this from Development: In Review to Development: Done in Stackable Engineering Jan 27, 2025
@Maleware
Copy link
Contributor

I've forgot to update dependencies in other operators. I'll reopen and link the PR's.

@NickLarsenNZ
Copy link
Member

Blocked by stackabletech/druid-operator#685

@NickLarsenNZ NickLarsenNZ added the release-note/action-required Denotes a PR that introduces potentially breaking changes that require user action. label Feb 5, 2025
dervoeti added a commit to stackabletech/druid-operator that referenced this issue Feb 5, 2025
@sbernauer sbernauer moved this from Development: Waiting for Review to Development: Done in Stackable Engineering Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note/action-required Denotes a PR that introduces potentially breaking changes that require user action. scheduled-for/25.3.0 status/blocked
Projects
Status: Development: Done
Development

No branches or pull requests

3 participants