From 52087f6ba08ce30ff48cc8cdfa4f69ca4b099bef Mon Sep 17 00:00:00 2001 From: swapnasagar pradhan Date: Sat, 7 Dec 2024 22:33:06 +0000 Subject: [PATCH] Resolving Review comments --- website/docs/design.md | 1 - website/versioned_docs/version-v0.7.x/design.md | 2 -- website/versioned_docs/version-v0.8.x/design.md | 1 - website/versioned_docs/version-v0.9.x/design.md | 2 -- 4 files changed, 6 deletions(-) diff --git a/website/docs/design.md b/website/docs/design.md index 7ddf17d4..36168420 100644 --- a/website/docs/design.md +++ b/website/docs/design.md @@ -76,7 +76,6 @@ type PackageManager interface { ## Tradeoffs -The core architectural choice of using packages as the unit of patching creates several constraints: 1. **Package-Based Update Model**: - While Copa can work with or without vulnerability scanner reports, its patching capability is fundamentally based on os-level package updates diff --git a/website/versioned_docs/version-v0.7.x/design.md b/website/versioned_docs/version-v0.7.x/design.md index b9756136..5b0c91c1 100644 --- a/website/versioned_docs/version-v0.7.x/design.md +++ b/website/versioned_docs/version-v0.7.x/design.md @@ -76,8 +76,6 @@ type PackageManager interface { ## Tradeoffs -The core architectural choice of using packages as the unit of patching creates several constraints: - 1. **Package-Based Update Model**: - While Copa can work with or without vulnerability scanner reports, its patching capability is fundamentally based on os-level package updates - When using scanner reports to perform a targeted patching of packages, false positives/negatives from scanners flow downstream to Copa diff --git a/website/versioned_docs/version-v0.8.x/design.md b/website/versioned_docs/version-v0.8.x/design.md index 1e89fb94..955599e0 100644 --- a/website/versioned_docs/version-v0.8.x/design.md +++ b/website/versioned_docs/version-v0.8.x/design.md @@ -76,7 +76,6 @@ type PackageManager interface { ## Tradeoffs -The core architectural choice of using packages as the unit of patching creates several constraints: 1. **Package-Based Update Model**: - While Copa can work with or without vulnerability scanner reports, its patching capability is fundamentally based on os-level package updates diff --git a/website/versioned_docs/version-v0.9.x/design.md b/website/versioned_docs/version-v0.9.x/design.md index b9756136..5b0c91c1 100644 --- a/website/versioned_docs/version-v0.9.x/design.md +++ b/website/versioned_docs/version-v0.9.x/design.md @@ -76,8 +76,6 @@ type PackageManager interface { ## Tradeoffs -The core architectural choice of using packages as the unit of patching creates several constraints: - 1. **Package-Based Update Model**: - While Copa can work with or without vulnerability scanner reports, its patching capability is fundamentally based on os-level package updates - When using scanner reports to perform a targeted patching of packages, false positives/negatives from scanners flow downstream to Copa