Visitar URL original
[META] Scorecard Enhancements Tracker · Issue #5339 · operator-framework/operator-sdk · GitHub
Skip to content

[META] Scorecard Enhancements Tracker #5339

Open

Description

@theishshah

This ticket is to track suggested improvements and bug-fixes to the scorecard. If an item is be explored, a new issue should be created and linked back here.

  • Disconnected environment scorecard images
  • Additional fields to track optional junit/xunit types
  • Support more/total environment configuration in SC config (eg. ServiceAccount)
  • Split scorecard run/environment configurations
  • Remove dependency on operator-framework/api updates for scorecard api changes
  • Create scorecard tests to verify operator capability levels

Activity

  1. added this to the Backlog milestone on Nov 2, 2021
  2. changed the title [-][META] Scorecard Enhacements Tracker[/-] [+][META] Scorecard Enhancements Tracker[/+] on Nov 11, 2021
  3. added
    scorecardIssue relates to the scorecard subcomponent
    on Nov 11, 2021
  4. jmccormick2001 commented on Nov 11, 2021

    @jmccormick2001
    Contributor

    long term you will want to consider moving out scorecard tests from the basic/olm suites that might be better implemented as static validations that the SDK validation can perform, that way it would focus scorecard on functional tests...something to consider long term, the pipelines already call the sdk's validate command as well to perform various static checks.

  5. jmccormick2001 commented on Nov 11, 2021

    @jmccormick2001
    Contributor

    you might also debate just splitting out the scorecard into its own repo, and then create a kubectl-like plugin to invoke scorecard from the sdk binary, another long term thing to consider doing.

  6. openshift-bot commented on Feb 15, 2022

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle stale

  7. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 15, 2022
  8. openshift-bot commented on Mar 17, 2022

    @openshift-bot

    Stale issues rot after 30d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle rotten.
    Rotten issues close after an additional 30d of inactivity.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle rotten
    /remove-lifecycle stale

  9. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Mar 17, 2022
  10. camilamacedo86 commented on Mar 18, 2022

    @camilamacedo86
    Contributor

    /lifecycle frozen

  11. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    on Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.needs discussionscorecardIssue relates to the scorecard subcomponent

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions