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

[cleanup/refactor] mv or resolve dso package #1109

Open
3 tasks
ccwienk opened this issue Jan 2, 2025 · 0 comments
Open
3 tasks

[cleanup/refactor] mv or resolve dso package #1109

ccwienk opened this issue Jan 2, 2025 · 0 comments
Labels
kind/enhancement Enhancement, improvement, extension kind/technical-debt Something that is only solved on the surface, but requires more (re)work to be done properly

Comments

@ccwienk
Copy link
Member

ccwienk commented Jan 2, 2025

Context / Motivation

dso package did not age well. There are a few remaining usages within cc-utils repository + a larger usage by ocm-gear. Long-term, the entire package should ideally be resolved. Mid-term, usages within cc-utils repository should ideally be removed + the package moved into delivery-service-repository.

Implementation Proposal

  • purge checkmarx package (including some usages of dso package)
  • either duplicate labels-definitions (dso.label), or mv into separate package/repository
  • decide where to mv delivery.client (either mv to delivery-service, or dedicated repository, or keep + duplicate model-classes)
@ccwienk ccwienk added kind/enhancement Enhancement, improvement, extension kind/technical-debt Something that is only solved on the surface, but requires more (re)work to be done properly labels Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement, improvement, extension kind/technical-debt Something that is only solved on the surface, but requires more (re)work to be done properly
Projects
None yet
Development

No branches or pull requests

1 participant