Skip to content

🌱 Add manifests directory - #2025

Merged
openshift-merge-bot[bot] merged 1 commit into
operator-framework:mainfrom
tmshort:new-manifests
Jun 12, 2025
Merged

🌱 Add manifests directory#2025
openshift-merge-bot[bot] merged 1 commit into
operator-framework:mainfrom
tmshort:new-manifests

Conversation

@tmshort

Copy link
Copy Markdown
Contributor

Check-in manifests to the manifests directory.
Currently, there is:

  • "standard" manifests, which is used as the basis for e2e and quickstart
  • "cluster-catalogs" manifests, which is just moved from the config dir

This is a quick/simple start to some of the Feature-Gated API work.

Description

Reviewer Checklist

  • API Go Documentation
  • Tests: Unit Tests (and E2E Tests, if appropriate)
  • Comprehensive Commit Messages
  • Links to related GitHub Issue(s)

@tmshort
tmshort requested a review from a team as a code ownerJune 12, 2025 18:46
@tmshort

Copy link
Copy Markdown
ContributorAuthor

/approve

@openshift-ciopenshift-ciBot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 12, 2025
@netlify

netlifyBot commented Jun 12, 2025

Copy link
Copy Markdown

Deploy Preview for olmv1 ready!

NameLink
🔨 Latest commitbdcbd4d
🔍 Latest deploy loghttps://app.netlify.com/projects/olmv1/deploys/684b3685bf2df300085210f3
😎 Deploy Previewhttps://deploy-preview-2025--olmv1.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Comment threadMakefile Outdated
# Generate the remaining catalogd manifests
$(CONTROLLER_GEN) --load-build-tags=$(GO_BUILD_TAGS) rbac:roleName=manager-role paths="./internal/catalogd/..." output:rbac:artifacts:config=$(KUSTOMIZE_CATD_RBAC_DIR)
$(CONTROLLER_GEN) --load-build-tags=$(GO_BUILD_TAGS) webhook paths="./internal/catalogd/..." output:webhook:artifacts:config=$(KUSTOMIZE_CATD_WEBHOOKS_DIR)
# Generate the checked-in manifests

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

nit: the use of the phrase "checked-in" here and in other places is most likely going to be a source of confusion for future maintainers. Maybe

Generate manifests to be committed to version control or Generate and store manifests in the manifests directory, for distribution ?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

"checked-in" is a very common term for code that's in source control.

Comment threadMakefile Outdated
quickstart: $(KUSTOMIZE) manifests #EXHELP Generate the unified installation release manifests and scripts.
$(KUSTOMIZE) build $(KUSTOMIZE_BUILD_DIR) | sed "s/cert-git-version/cert-$(VERSION)/g" | sed "s/:devel/:$(VERSION)/g" > $(RELEASE_MANIFEST)
quickstart: manifests #EXHELP Generate the unified installation release manifests and scripts.
# Update the image version in the standard manifests

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
# Update the image version in the standard manifests
# Update the image version in the stored manifests

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

The use use of the term "standard" is a reflection of the nature of the manifests as described in the Feature Gated APIs RFC.

Check-in manifests to the manifests directory.
Currently, there is:
* "standard" manifests, which is used as the basis for e2e and quickstart
* "cluster-catalogs" manifests, which is just moved from the config dir
Signed-off-by: Todd Short <tshort@redhat.com>

@anik120anik120 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/lgtm

@openshift-ciopenshift-ciBot added the lgtm Indicates that a PR is ready to be merged. label Jun 12, 2025
@openshift-ci

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120, tmshort

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@codecov

codecovBot commented Jun 12, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.28%. Comparing base (1a27741) to head (bdcbd4d).
Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #2025 +/- ##
=======================================
Coverage 69.28% 69.28% =======================================
Files 79 79 Lines 7051 7051 =======================================
Hits 4885 4885 Misses 1884 1884 Partials 282 282 
FlagCoverage Δ
e2e43.00% <ø> (+0.05%)⬆️
unit60.19% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@openshift-merge-bot
openshift-merge-botBot merged commit b004bc2 into operator-framework:mainJun 12, 2025
@tmshort
tmshort deleted the new-manifests branch June 12, 2025 23:37
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approvedIndicates a PR has been approved by an approver from all required OWNERS files.lgtmIndicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@tmshort@anik120