Skip to content

Further CNCF Defender Actions #1465

Closed as not planned
Closed as not planned
Further CNCF Defender Actions#1465
Labels
area/alizerEnhancement or issue related to the alizer repoarea/apiEnhancement or issue related to the api/devfile specificationarea/landing-pageIssues with the Landing Pagearea/libraryCommon devfile library for interacting with devfilesarea/registryDevfile registry for stacks and infrastructurekind/epicA high level requirement that can/should be split into smaller issueskind/user-storyUser story for new enhancementlifecycle/rottenRotten items. These items have been stale for 60 days and are now closed.lifecycle/staleStale items. These items have not been updated for 90 days.

Description

@Jdubrick
Jdubrick
opened on Mar 1, 2024

/kind user-story

Which area this user story is related to?

/area api
/area library
/area registry
/area alizer
/area landing-page

User Story

In continuation of the CNCF Defender there are 3 checks that need further investigation:

  1. Software Bill of Materials (SBOM)
  2. Signed Releases
  3. Token Permissions

We need to determine whether these 3 checks are relevant to our repositories, and if so, create issues to implement them. If they are not relevant we will need to create issues for marking them as exempt.

An initial spike issue has been linked to this epic to determine the path required.

Acceptance Criteria

Activity

  1. Jdubrick
    added
    kind/epicA high level requirement that can/should be split into smaller issues
    on Mar 1, 2024
  2. Jdubrick
    added this to Devfile Projecton Mar 1, 2024
  3. openshift-ci
    added
    kind/user-storyUser story for new enhancement
    area/apiEnhancement or issue related to the api/devfile specification
    area/libraryCommon devfile library for interacting with devfiles
    area/registryDevfile registry for stacks and infrastructure
    area/alizerEnhancement or issue related to the alizer repo
    area/landing-pageIssues with the Landing Page
    on Mar 1, 2024
  4. michael-valdron
    moved this to Refinement in Devfile Projecton Mar 21, 2024

  5. github-actions commented on Sep 30, 2024

    @github-actions
    github-actionsbot
    on Sep 30, 2024 – with GitHub Actions

    This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

  6. github-actions
    added
    lifecycle/staleStale items. These items have not been updated for 90 days.
    on Sep 30, 2024
  7. github-actions
    added
    lifecycle/rottenRotten items. These items have been stale for 60 days and are now closed.
    on Nov 30, 2024
  8. github-actions
    closed this as not plannedon Nov 30, 2024
  9. github-project-automation
    moved this from Refinement to Done ✅ in Devfile Projecton Nov 30, 2024
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

    area/alizerEnhancement or issue related to the alizer repoarea/apiEnhancement or issue related to the api/devfile specificationarea/landing-pageIssues with the Landing Pagearea/libraryCommon devfile library for interacting with devfilesarea/registryDevfile registry for stacks and infrastructurekind/epicA high level requirement that can/should be split into smaller issueskind/user-storyUser story for new enhancementlifecycle/rottenRotten items. These items have been stale for 60 days and are now closed.lifecycle/staleStale items. These items have not been updated for 90 days.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions