-
Notifications
You must be signed in to change notification settings - Fork 565
[CCXDEV-15259]: promote InsightConfigAPI and OnDemandDataGather to v1 #2448
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
base: master
Are you sure you want to change the base?
Conversation
Hello @opokornyy! Some important instructions when contributing to openshift/api: |
/retest |
/test verify-feature-promotion |
d7b46b0
to
dce787e
Compare
dce787e
to
337fbf2
Compare
382e32d
to
c47f3e9
Compare
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]>
Signed-off-by: Ondrej Pokorny <[email protected]>
c47f3e9
to
d29ee57
Compare
a2b2dec
to
e34bacd
Compare
/retest |
e34bacd
to
c3bd449
Compare
Signed-off-by: Ondrej Pokorny <[email protected]>
c3bd449
to
43fc93f
Compare
/retest |
@opokornyy Is this still WIP? If not, would you mind dropping the |
/retest |
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. |
/retest |
There was a problem hiding this 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?
cf53f5d
to
4a43f0f
Compare
/approve /hold for @everettraven in case he has any further comments |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple comments
With agreement from Joel on the status subresource removal, once the changes from my review are made this LGTM |
/approve cancel Realised I missed the second set of types being promoted on my last review |
Ah, I missed this as well 🤦 |
There was a problem hiding this 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
insights/v1/types_insights.go
Outdated
// 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"` |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
4a43f0f
to
654c441
Compare
[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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
654c441
to
fc30ba4
Compare
Hey, I think I’ve addressed all the comments, so it should be ready for another round of reviews. @JoelSpeed @everettraven |
There was a problem hiding this 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.
insights/v1/tests/datagathers.insights.openshift.io/InsightsOnDemandDataGather.yaml
Outdated
Show resolved
Hide resolved
fc30ba4
to
596ed30
Compare
/retest |
Signed-off-by: Ondrej Pokorny <[email protected]>
596ed30
to
25581c4
Compare
@opokornyy: The following tests failed, say
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. |
Hey @JoelSpeed, @everettraven all comments should be resolved now. |
No description provided.