Skip to content

Conversation

opokornyy
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 12, 2025
Copy link
Contributor

openshift-ci bot commented Aug 12, 2025

Hello @opokornyy! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@openshift-ci openshift-ci bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Aug 12, 2025
@openshift-ci openshift-ci bot requested review from deads2k and everettraven August 12, 2025 14:24
@opokornyy
Copy link
Contributor Author

/retest

@opokornyy
Copy link
Contributor Author

/test verify-feature-promotion

@opokornyy opokornyy force-pushed the CCXDEV-15259-io-v1 branch 2 times, most recently from d7b46b0 to dce787e Compare August 15, 2025 09:48
@opokornyy opokornyy changed the title WIP: promote InsightConfigAPI and OnDemandDataGather to v1 WIP: [CCXDEV-15259]: promote InsightConfigAPI and OnDemandDataGather to v1 Aug 15, 2025
@opokornyy opokornyy force-pushed the CCXDEV-15259-io-v1 branch 2 times, most recently from 382e32d to c47f3e9 Compare August 19, 2025 08:08
Signed-off-by: Ondrej Pokorny <[email protected]>
Signed-off-by: Ondrej Pokorny <[email protected]>
Signed-off-by: Ondrej Pokorny <[email protected]>
Signed-off-by: Ondrej Pokorny <[email protected]>
@opokornyy
Copy link
Contributor Author

/retest

Signed-off-by: Ondrej Pokorny <[email protected]>
@opokornyy
Copy link
Contributor Author

/retest

@everettraven
Copy link
Contributor

@opokornyy Is this still WIP? If not, would you mind dropping the WIP: from the title?

@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 10, 2025
@opokornyy
Copy link
Contributor Author

/retest

@opokornyy
Copy link
Contributor Author

@opokornyy Is this still WIP? If not, would you mind dropping the WIP: from the title?

Sure, I forgot to drop that. Should I still keep it as a draft as well?

@everettraven
Copy link
Contributor

everettraven commented Sep 10, 2025

Sure, I forgot to drop that. Should I still keep it as a draft as well?

If you think this is ready to review for merge, it should not be a draft. If this is something you don't yet want reviews on a draft is appropriate.

@opokornyy
Copy link
Contributor Author

/retest

Copy link
Contributor

@JoelSpeed JoelSpeed left a comment

Choose a reason for hiding this comment

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

Have done a more thorough review today of the text and godoc, if you can apply my suggestions, I think we are ready to merge this.

Do we have a feature promotion PR that accompanies this to show what the feature promotion data might look like?

@JoelSpeed
Copy link
Contributor

/approve

/hold for @everettraven in case he has any further comments

@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 11, 2025
Copy link
Contributor

@everettraven everettraven left a comment

Choose a reason for hiding this comment

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

A couple comments

@everettraven
Copy link
Contributor

With agreement from Joel on the status subresource removal, once the changes from my review are made this LGTM

@JoelSpeed
Copy link
Contributor

/approve cancel

Realised I missed the second set of types being promoted on my last review

@openshift-ci openshift-ci bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 11, 2025
@everettraven
Copy link
Contributor

Realised I missed the second set of types being promoted on my last review

Ah, I missed this as well 🤦

Copy link
Contributor

@everettraven everettraven left a comment

Choose a reason for hiding this comment

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

A couple more comments from the types I missed on my last review round

// When omitted, this means no data gathering has taken place yet or the
// corresponding Insights analysis (identified by "insightsRequestID") is not available.
// +optional
InsightsReport *InsightsReport `json:"insightsReport,omitempty"`
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a semantic difference between insightsReport: {} and it being omitted?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think there is no difference. Should I change this field somehow?

Copy link
Contributor

Choose a reason for hiding this comment

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

You'll need to remove the pointer and add the omitzero tag.

In order to do that, you'll need to update the InsightsReport type to require some sub-field being specified.

Does it ever make sense for the InsightsReport type to only contain a subset of the fields allowed in its type?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Our operator is setting this field and I think we can make the downloadedTime and uri required, because we are always setting these two fields and healthChecks would be the only optional field here.

Copy link
Contributor

openshift-ci bot commented Sep 16, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

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

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

@opokornyy
Copy link
Contributor Author

Hey, I think I’ve addressed all the comments, so it should be ready for another round of reviews. @JoelSpeed @everettraven

Copy link
Contributor

@everettraven everettraven left a comment

Choose a reason for hiding this comment

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

A couple more godoc only comments.

Other than that, this looks fine to me.

@opokornyy
Copy link
Contributor Author

/retest

Signed-off-by: Ondrej Pokorny <[email protected]>
Copy link
Contributor

openshift-ci bot commented Sep 22, 2025

@opokornyy: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-serial-techpreview-1of2 4a43f0f link true /test e2e-aws-serial-techpreview-1of2
ci/prow/e2e-gcp 4a43f0f link false /test e2e-gcp
ci/prow/e2e-aws-ovn-techpreview 4a43f0f link true /test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-ovn 4a43f0f link true /test e2e-aws-ovn
ci/prow/e2e-aws-ovn-hypershift 4a43f0f link true /test e2e-aws-ovn-hypershift
ci/prow/e2e-aws-serial-techpreview-2of2 4a43f0f link true /test e2e-aws-serial-techpreview-2of2
ci/prow/okd-scos-e2e-aws-ovn 25581c4 link false /test okd-scos-e2e-aws-ovn
ci/prow/minor-e2e-upgrade-minor 25581c4 link true /test minor-e2e-upgrade-minor

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@opokornyy
Copy link
Contributor Author

Hey @JoelSpeed, @everettraven all comments should be resolved now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants