Skip to content

Conversation

@michaelryanpeter
Copy link
Contributor

Description

Helping @perdasilva by updating the docs strings for the API definitions.

🤞 I did this right :)

Reviewer Checklist

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

@michaelryanpeter michaelryanpeter requested a review from a team as a code owner November 24, 2025 15:18
@netlify
Copy link

netlify bot commented Nov 24, 2025

Deploy Preview for olmv1 ready!

Name Link
🔨 Latest commit 7b384be
🔍 Latest deploy log https://app.netlify.com/projects/olmv1/deploys/6943c70586d89b0008855456
😎 Deploy Preview https://deploy-preview-2359--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.

@codecov
Copy link

codecov bot commented Nov 24, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.82%. Comparing base (c5d9fed) to head (7b384be).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2359      +/-   ##
==========================================
+ Coverage   68.79%   68.82%   +0.02%     
==========================================
  Files         100      100              
  Lines        7641     7641              
==========================================
+ Hits         5257     5259       +2     
+ Misses       1948     1947       -1     
+ Partials      436      435       -1     
Flag Coverage Δ
e2e 43.81% <ø> (-0.09%) ⬇️
experimental-e2e 13.68% <ø> (ø)
unit 57.11% <ø> (+0.01%) ⬆️

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.

@michaelryanpeter michaelryanpeter force-pushed the docs-simplify-cc-ce branch 2 times, most recently from 94c502d to 91daf1f Compare November 24, 2025 16:40
@tmshort
Copy link
Contributor

tmshort commented Nov 25, 2025

The CRD diff is only the text.

@tmshort
Copy link
Contributor

tmshort commented Nov 25, 2025

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 25, 2025
//+kubebuilder:printcolumn:name=Age,type=date,JSONPath=`.metadata.creationTimestamp`

// ClusterCatalog enables users to make File-Based Catalog (FBC) catalog data available to the cluster.
// The ClusterCatalog resource makes File-Based Catalog (FBC) data available to your cluster.
Copy link
Contributor

Choose a reason for hiding this comment

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

We should follow the godoc format where the comment starts with name of the property/field as it was =/
I learned this recently in the ClusterExtensionRevision API doc

Copy link
Contributor

Choose a reason for hiding this comment

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

Comment on lines 63 to 65
// The spec field defines the desired state of the ClusterCatalog.
// The spec field is required.
// The controller ensures that the catalog is unpacked and served over the catalog content HTTP server.
Copy link
Contributor

@perdasilva perdasilva Dec 2, 2025

Choose a reason for hiding this comment

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

Since these docs will be converted into docs for the users with kubectl explain, we use the user face facing field name, i.e. lowercase (i.e. instead of // Spec we do // spec)

Suggested change
// The spec field defines the desired state of the ClusterCatalog.
// The spec field is required.
// The controller ensures that the catalog is unpacked and served over the catalog content HTTP server.
// spec is a required field that defines the desired state of the ClusterCatalog.
// The controller ensures that the catalog is unpacked and served over the catalog content HTTP server.

Copy link
Contributor

@perdasilva perdasilva left a comment

Choose a reason for hiding this comment

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

It seems we should follow the godoc standard with the yaml field names (lowercase) by convention. I've left a couple of illustrative suggestions. If we make those slight adjustments, everything else should be ok, I think.

@tmshort
Copy link
Contributor

tmshort commented Dec 9, 2025

This needs to be rebased, and that will also fix the e2e issues.

@michaelryanpeter
Copy link
Contributor Author

Heard. I am going to update this PR and refactor my downstream slash command for godocs formatting. Hopefully, I can get this completed before shutdown. This was a one-off bit of untracked work for me, and a handful of other things popped up that are more urgent.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 13, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 17, 2025
@perdasilva perdasilva removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 18, 2025
@perdasilva
Copy link
Contributor

/approve

@perdasilva perdasilva self-requested a review December 18, 2025 09:20
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 18, 2025
Copy link
Contributor

@pedjak pedjak left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 18, 2025
@pedjak
Copy link
Contributor

pedjak commented Dec 18, 2025

/override crd-diff/crd-diff

@openshift-ci
Copy link

openshift-ci bot commented Dec 18, 2025

@pedjak: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • crd-diff/crd-diff

Only the following failed contexts/checkruns were expected:

  • Verify PR title
  • crd-diff
  • e2e
  • experimental-e2e
  • extension-developer-e2e
  • go-apidiff
  • go-verdiff
  • goreleaser
  • lint
  • netlify/olmv1/deploy-preview
  • st2ex-e2e
  • tide
  • unit-test-basic
  • upgrade-st2st-e2e
  • verify

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override crd-diff/crd-diff

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@pedjak
Copy link
Contributor

pedjak commented Dec 18, 2025

/override crd-diff

@openshift-ci
Copy link

openshift-ci bot commented Dec 18, 2025

@pedjak: Overrode contexts on behalf of pedjak: crd-diff

Details

In response to this:

/override crd-diff

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci
Copy link

openshift-ci bot commented Dec 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pedjak, perdasilva, 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

@openshift-merge-bot openshift-merge-bot bot merged commit aea576c into operator-framework:main Dec 18, 2025
28 of 29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants