remove SBOMSummary creation

[matthyx]

Type

enhancement

---

Description

• Simplified SBOM storage logic by renaming storeSBOMWithContent to StoreSBOM and removing the unused storeSBOMWithoutContent function.
• Removed the test case for the deleted storeSBOMWithoutContent function.
• Updated dependencies to newer versions, including github.com/kubescape/k8s-interface, github.com/kubescape/storage, k8s.io/apimachinery, and k8s.io/client-go.
• Updated checksums in go.sum for the updated dependencies.

---

Changes walkthrough

	Relevant files
Enhancement	apiserver.go Simplify SBOM Storage Logic by Removing Redundant Function repositories/apiserver.go Renamed storeSBOMWithContent to StoreSBOM. Removed storeSBOMWithoutContent function and its invocation, simplifying SBOM storage logic. +1/-54
Tests	apiserver_test.go Remove Test for Deleted SBOM Storage Function                        repositories/apiserver_test.go Removed test case TestAPIServerStore_storeSBOMWithoutContent corresponding to the removed function. +0/-11
Dependencies	go.mod Update Dependencies for Simplified SBOM Storage                    go.mod Updated dependencies: github.com/kubescape/k8s-interface to v0.0.162, github.com/kubescape/storage to v0.0.70-0.20240326141707-6bd88c6857f3, k8s.io/apimachinery to v0.29.0, and k8s.io/client-go to v0.29.0. Updated indirect dependencies, including golang.org/x/crypto to v0.19.0 and golang.org/x/sys to v0.17.0. +8/-8      go.sum Update Checksums for Updated Dependencies                                go.sum Updated checksums for the direct and indirect dependencies that were updated in go.mod. +20/-20

---

✨ PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-free]

PR Description updated to latest commit (ab1637d)

[codiumai-pr-agent-free]

PR Review

⏱️ Estimated effort to review [1-5]	2, because the changes are straightforward and involve renaming a function, removing an unused function, and updating dependencies. The removal of a test case corresponding to the deleted function is also a simple change. The updates in dependencies and checksums in go.sum are routine maintenance tasks that do not require in-depth review.
🧪 Relevant tests	No
🔍 Possible issues	Possible Regression: Renaming storeSBOMWithContent to StoreSBOM and removing storeSBOMWithoutContent simplifies the code but ensure that all references to these functions are updated accordingly to prevent runtime errors.
	Dependency Updates: The update of dependencies introduces changes from external sources. It's important to ensure that these updates do not introduce breaking changes or vulnerabilities.
🔒 Security concerns	No

---

✨ Review tool usage guide:

---

Overview:
The review tool scans the PR code changes, and generates a PR review which includes several types of feedbacks, such as possible PR issues, security threats and relevant test in the PR. More feedbacks can be added by configuring the tool.

The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.

• When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

• With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

See the review usage page for a comprehensive guide on using this tool.

[codiumai-pr-agent-free]

PR Code Suggestions

Category	Suggestions
Best practice	Add error handling for the OpenTelemetry tracer start function. Consider adding error handling for the otel.Tracer("").Start function call. If it fails, it might be important to handle the error or log it, rather than proceeding with the execution as if it succeeded. repositories/apiserver.go [866] -_, span := otel.Tracer("").Start(ctx, "APIServerStore.StoreSBOMWithContent") +ctx, span, err := otel.Tracer("").Start(ctx, "APIServerStore.StoreSBOMWithContent") +if err != nil { + // handle or log the error +}
Enhancement	Verify compatibility of updated dependencies. Ensure that the updated dependencies github.com/kubescape/k8s-interface v0.0.162 and github.com/kubescape/storage v0.0.70-0.20240326141707-6bd88c6857f3 are compatible with your project. Test thoroughly to avoid potential integration issues due to the dependency updates. go.mod [28-29] +// Ensure compatibility and test thoroughly github.com/kubescape/k8s-interface v0.0.162 github.com/kubescape/storage v0.0.70-0.20240326141707-6bd88c6857f3
Security	Check for deprecated functions after updating golang.org/x/crypto. After updating golang.org/x/crypto to v0.19.0, ensure that there are no deprecated functions being used in your project. This version might introduce breaking changes or deprecations that could affect your project's security or functionality. go.mod [313] +// Check for deprecated functions or breaking changes golang.org/x/crypto v0.19.0 // indirect
Maintainability	Review and manage indirect dependencies efficiently. Consider reviewing the necessity of the indirect dependencies added in this PR. If they are not directly used by your project, try to minimize dependency bloat by removing or managing them more efficiently. go.mod [319-320] +// Review and potentially remove unnecessary indirect dependencies golang.org/x/sys v0.17.0 // indirect golang.org/x/term v0.17.0 // indirect
Possible issue	Ensure Kubernetes interactions remain functional after dependency updates. After updating Kubernetes-related dependencies to v0.29.0, it's crucial to ensure that your project's Kubernetes interactions remain functional. This update might introduce changes that could impact how your application interacts with Kubernetes APIs. go.mod [37-38] +// Ensure Kubernetes interactions remain functional after the update k8s.io/apimachinery v0.29.0 k8s.io/client-go v0.29.0

---

✨ Improve tool usage guide:

---

Overview:
The improve tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.

• When commenting, to edit configurations related to the improve tool (pr_code_suggestions section), use the following template:

/improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=...

• With a configuration file, use the following template:

[pr_code_suggestions]
some_config1=...
some_config2=...

See the improve usage page for a comprehensive guide on using this tool.

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success