Skip to content
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

Reduce component reconciler's action verbosity #1388

Open
wants to merge 4 commits into
base: feature-operator-refactor
Choose a base branch
from

Conversation

lburgazzoli
Copy link
Contributor

@lburgazzoli lburgazzoli commented Nov 21, 2024

Description

How Has This Been Tested?

Screenshot or short clip

Merge criteria

  • You have read the contributors guide.
  • Commit messages are meaningful - have a clear and concise summary and detailed explanation of what was changed and why.
  • Pull Request contains a description of the solution, a link to the JIRA issue, and to any dependent or related Pull Request.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

Copy link

codecov bot commented Nov 21, 2024

Codecov Report

Attention: Patch coverage is 81.42857% with 13 lines in your changes missing coverage. Please review.

Please upload report for BASE (feature-operator-refactor@89bf20a). Learn more about missing BASE report.

Files with missing lines Patch % Lines
pkg/controller/actions/deploy/action_deploy.go 84.21% 5 Missing and 1 partial ⚠️
pkg/controller/actions/gc/action_gc.go 78.57% 2 Missing and 1 partial ⚠️
...oller/actions/updatestatus/action_update_status.go 72.72% 2 Missing and 1 partial ⚠️
pkg/controller/actions/gc/action_gc_support.go 85.71% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@                     Coverage Diff                      @@
##             feature-operator-refactor    #1388   +/-   ##
============================================================
  Coverage                             ?   27.12%           
============================================================
  Files                                ?       60           
  Lines                                ?     4811           
  Branches                             ?        0           
============================================================
  Hits                                 ?     1305           
  Misses                               ?     3354           
  Partials                             ?      152           

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

Copy link
Member

@zdtsw zdtsw left a comment

Choose a reason for hiding this comment

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

LGTM

deploy.WithLabel(labels.ComponentPartOf, componentsv1.DashboardInstanceName),
)).
WithAction(updatestatus.NewAction(
updatestatus.WithSelectorLabel(labels.ComponentPartOf, componentsv1.DashboardInstanceName),
Copy link
Member

Choose a reason for hiding this comment

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

I have a tangential question - Is there a reason for labels to be components.opendatahub.io/part-of:default-dashboard instead of components.opendatahub.io/part-of:dashboard ?

Copy link
Member

Choose a reason for hiding this comment

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

i guess the question is:
should the value be the name of the component CR or the name of the component kind ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, the way we use labels should be cleaned up a little bit :) , so as today we use the instance name because that label is used by predicates and event mapper and some actions but I think the right path would be to:

  • use the Kind for the part-of
  • add some additional annotations for other stuffs (predicated, mapper, etc)

@VaishnaviHire
Copy link
Member

/lgtm

Copy link

openshift-ci bot commented Nov 26, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zdtsw

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

The pull request process is described 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

@openshift-ci openshift-ci bot removed the lgtm label Nov 26, 2024
Copy link

openshift-ci bot commented Nov 26, 2024

New changes are detected. LGTM label has been removed.

@lburgazzoli lburgazzoli marked this pull request as ready for review November 26, 2024 18:28
@lburgazzoli
Copy link
Contributor Author

/test opendatahub-operator-e2e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

Successfully merging this pull request may close these issues.

3 participants