Repository navigation
Conversation
Start the OPRUN-4850 discussion with a minimal content-storage contract, validation boundaries, ownership expectations, and incremental follow-ups. Include the generated API reference alongside the design document. Signed-off-by: Fabricio Aguiar <fabricio.aguiar@gmail.com> rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED
Introduce experimental immutable manifest storage with ClusterObjectSliceEntry values. Validate the envelope through schema and CEL rules and add API tests and experimental chart wiring. Deep payload admission, consumer integration, and retention remain separate follow-ups for OPRUN-4850. Signed-off-by: Fabricio Aguiar <fabricio.aguiar@gmail.com> rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED
Generate the experimental CRD, deep-copy methods, apply configurations, and experimental installation manifests from the initial ClusterObjectSlice API definition. The generated API reference is in the documentation commit. Signed-off-by: Fabricio Aguiar <fabricio.aguiar@gmail.com> rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED
👷 Deploy request for olmv1 pending review.Visit the deploys page to approve it
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
|
This branch has not been deployed
This file contains hidden or 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
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.
Description
Start the OPRUN-4850 design discussion with documentation and an initial experimental
ClusterObjectSliceAPI for storing rendered manifests independently of rollout intent. Existing inline and Secret-backed content paths continue to work as they do today.JSON/GzipJSONpayloads. Schema and CEL validate the storage envelope; payload parsing, decompression, and identity comparison remain follow-up work.This draft is a conversation starter. Readable manifests, deeper admission validation, COD/COS references, digests, and retention coordination remain open for incremental proposals. Creating a slice stores content without applying objects or reporting rollout readiness.
Documentation is in one commit, followed by separate commits for API source/tests and generated code/manifests.
Related issue: https://redhat.atlassian.net/browse/OPRUN-4850
Validation
make test-unitmake lint lint-helmmake lint-api-diff— no new issues; 32 pre-existing issuesmake verifyReviewer Checklist
Always review AI generated responses prior to use.
AI-assisted response via openshift-developer plugin