Skip to content

Releases: kubescape/storage

Release v0.0.59

17 Jan 06:03
@github-actions github-actions
v0.0.59
3172a8c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v0.0.59

User description

Sorry, we do not accept changes directly against this repository. Please see
CONTRIBUTING.md for information on where and how to contribute instead.

Type

Bug fix

Description

  • Added a condition in syfttypes.go and v1beta1/syfttypes.go to return nil if the Type field is empty, which can occur in some cases such as when the object is returned from the watcher.
  • Updated the required fields for several schemas in zz_generated.openapi.go, removing some previously required fields.
  • Updated the version of the github.com/kubescape/k8s-interface package in go.mod and updated the corresponding checksums in go.sum.

Changes walkthrough

Relevant files                                                                                                                                 
Bug fix
syfttypes.go                                                                                               
    pkg/apis/softwarecomposition/syfttypes.go

    Added a condition to return nil if the Type field is
    empty, which can occur in some cases such as when the object
    is returned from the watcher.

 +5/-0
syfttypes.go                                                                                               
    pkg/apis/softwarecomposition/v1beta1/syfttypes.go

    Similar to the previous file, a condition was added to
    return nil if the Type field is empty.

 +5/-0
zz_generated.openapi.go                                                                         
    pkg/generated/openapi/zz_generated.openapi.go

    Updated the required fields for several schemas, removing
    some previously required fields.

 +5/-6
Dependencies
go.mod                                                                                                           
    go.mod

    Updated the version of the
    github.com/kubescape/k8s-interface package.

 +1/-1
go.sum                                                                                                           
    go.sum

    Updated the checksums for the
    github.com/kubescape/k8s-interface package due to the
    version update.

 +2/-2
✨ Usage guide:

Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. 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 describe tool (pr_description section), use the following template:

/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:

[pr_description]
some_config1=...
some_config2=...
Enabling\disabling automation
  • When you first install the app, the default mode for the describe tool is:
pr_commands = ["/describe --pr_description.add_original_user_description=true" 
                         "--pr_description.keep_original_user_title=true", ...]

meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.

  • Markers are an alternative way to control the generated description, to give maximal control to the user. If you set:
pr_commands = ["/describe --pr_description.use_description_markers=true", ...]

the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following:

  • type: the PR type.
  • summary: the PR summary.
  • walkthrough: the PR walkthrough.

Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

Custom labels

The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other].

If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:

  • Main topic:performance - pr_agent:The main topic of this PR is performance
  • New endpoint - pr_agent:A new endpoint was added in this PR
  • SQL query - pr_agent:A new SQL query was added in this PR
  • Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile
  • ...

The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

Utilizing extra instructions

The describe tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.

Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.

Examples for extra instructions:

[pr_description] 
extra_instructions="""
- The PR title should be in the format: '<PR type>: <title>'
- The title should be short and concise (up to 10 words)
- ...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

  • /review: Request a review of your Pull Request.
  • /describe: Update the PR title and description based on the contents of the PR.
  • /improve [--extended]: Suggest code improvements. Extended mode provides a higher qual...
Read more
Assets 2
Loading

Release v0.0.58

14 Jan 13:57
@github-actions github-actions
v0.0.58
1893c8b
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v0.0.58

User description

Sorry, we do not accept changes directly against this repository. Please see
CONTRIBUTING.md for information on where and how to contribute instead.

Type

Enhancement

Description

  • Added a new file labels.go that contains a map of labels that should be ignored and a function to check if a label is in the ignore list.
  • Modified the networkpolicy.go file to include a call to the removeLabels function, which removes ignored labels from the PodSelector in both generateEgressRule and generateIngressRule functions. The removeLabels function was also added, which removes labels from a given map if they are in the ignore list.
  • Updated the networkpolicy_test.go file to include ignored labels in the test cases for the TestGenerateNetworkPolicy function.

Changes walkthrough

Relevant files                                                                                                                                 
Enhancement
labels.go                                                                                                     
    pkg/apis/softwarecomposition/networkpolicy/labels.go

    This file was added to the project. It contains a map of
    labels that should be ignored and a function
    isIgnoredLabel to check if a label is in the ignore list.

 +29/-0
networkpolicy.go                                                                                       
    pkg/apis/softwarecomposition/networkpolicy/networkpolicy.go

    This file was modified to include a call to the
    removeLabels function, which removes ignored labels from
    the PodSelector in both generateEgressRule and
    generateIngressRule functions. The removeLabels function
    was also added, which removes labels from a given map if
    they are in the ignore list.

 +11/-0
Tests
networkpolicy_test.go                                                                             
    pkg/apis/softwarecomposition/networkpolicy/networkpolicy_test.go

    This file was modified to include ignored labels in the test
    cases for the TestGenerateNetworkPolicy function.

 +10/-4
✨ Usage guide:

Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. 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 describe tool (pr_description section), use the following template:

/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:

[pr_description]
some_config1=...
some_config2=...
Enabling\disabling automation
  • When you first install the app, the default mode for the describe tool is:
pr_commands = ["/describe --pr_description.add_original_user_description=true" 
                         "--pr_description.keep_original_user_title=true", ...]

meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.

  • Markers are an alternative way to control the generated description, to give maximal control to the user. If you set:
pr_commands = ["/describe --pr_description.use_description_markers=true", ...]

the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following:

  • type: the PR type.
  • summary: the PR summary.
  • walkthrough: the PR walkthrough.

Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

Custom labels

The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other].

If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:

  • Main topic:performance - pr_agent:The main topic of this PR is performance
  • New endpoint - pr_agent:A new endpoint was added in this PR
  • SQL query - pr_agent:A new SQL query was added in this PR
  • Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile
  • ...

The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

Utilizing extra instructions

The describe tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.

Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.

Examples for extra instructions:

[pr_description] 
extra_instructions="""
- The PR title should be in the format: '<PR type>: <title>'
- The title should be short and concise (up to 10 words)
- ...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

  • /review: Request a review of your Pull Request.
  • /describe: Update the PR title and description based on the contents of the PR.
  • /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
  • /ask <QUESTION>: Ask a question about the PR.
  • /update_changelog: Update the changelog based on the PR's contents.
  • /add_docs 💎: Generate docstring for new components introduced in the PR.
  • /generate_labels 💎: Generate labels for the PR based on the PR's contents.
  • /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

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

Assets 2
Loading

Release v0.0.57

11 Jan 07:30
@github-actions github-actions
v0.0.57
e7f57fa
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v0.0.57

Type

Enhancement

Description

This PR introduces changes to the way metadata is handled within the pkg/registry/file/storage.go file. The main changes include:

  • Replacing the out parameter with metaOut in several functions to store only metadata instead of the entire object.
  • Updating the watchDispatcher calls to use metaOut instead of obj or out.
  • Modifying the writeFiles, Create, Delete, and GuaranteedUpdate functions to accommodate the above changes.

Changes walkthrough

Relevant files                                                                                                                                 
Enhancement
storage.go                                                                                                   
    pkg/registry/file/storage.go

    The changes in this file are primarily focused on modifying
    the way metadata is handled within various functions. The
    out parameter, which was previously used to store the
    output of certain operations, has been replaced with
    metaOut. This new parameter is used to store only
    metadata, rather than the entire object. This change is
    reflected in the writeFiles, Create, Delete, and
    GuaranteedUpdate functions. Additionally, the
    watchDispatcher calls have been updated to use metaOut
    instead of obj or out.

 +17/-17
✨ Usage guide:

Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. 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 describe tool (pr_description section), use the following template:

/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:

[pr_description]
some_config1=...
some_config2=...
Enabling\disabling automation
  • When you first install the app, the default mode for the describe tool is:
pr_commands = ["/describe --pr_description.add_original_user_description=true" 
                         "--pr_description.keep_original_user_title=true", ...]

meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.

  • Markers are an alternative way to control the generated description, to give maximal control to the user. If you set:
pr_commands = ["/describe --pr_description.use_description_markers=true", ...]

the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following:

  • type: the PR type.
  • summary: the PR summary.
  • walkthrough: the PR walkthrough.

Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

Custom labels

The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other].

If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:

  • Main topic:performance - pr_agent:The main topic of this PR is performance
  • New endpoint - pr_agent:A new endpoint was added in this PR
  • SQL query - pr_agent:A new SQL query was added in this PR
  • Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile
  • ...

The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

Utilizing extra instructions

The describe tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.

Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.

Examples for extra instructions:

[pr_description] 
extra_instructions="""
- The PR title should be in the format: '<PR type>: <title>'
- The title should be short and concise (up to 10 words)
- ...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

  • /review: Request a review of your Pull Request.
  • /describe: Update the PR title and description based on the contents of the PR.
  • /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
  • /ask <QUESTION>: Ask a question about the PR.
  • /update_changelog: Update the changelog based on the PR's contents.
  • /add_docs 💎: Generate docstring for new components introduced in the PR.
  • /generate_labels 💎: Generate labels for the PR based on the PR's contents.
  • /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

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

Assets 2
Loading

Release v0.0.56

10 Jan 14:56
@github-actions github-actions
v0.0.56
b28bc8e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v0.0.56

User description

Sorry, we do not accept changes directly against this repository. Please see
CONTRIBUTING.md for information on where and how to contribute instead.

Type

Enhancement

Description

  • Refactored the GenerateNetworkPolicy function in networkpolicy.go to use the v1beta1 version of NetworkNeighbors and KnownServer. The function now converts these objects to their v1 counterparts, generates the network policy using the v1 objects, and then converts the generated policy back to v1beta1.
  • Added the functions convertGeneratedNetworkPolicy, convertNetworkNeighbors, and convertKnownServersList to handle these conversions.
  • Updated the test TestGeneratedNetworkPolicyStorage_Get in generatednetworkpolicy_test.go to reflect the changes in the GeneratedNetworkPolicy object. The APIVersion has been updated from spdx.softwarecomposition.kubescape.io/v1beta1 to spdx.softwarecomposition.kubescape.io.
  • Updated the import paths for softwarecomposition and networkpolicy in generatednetworkpolicy.go to reflect the changes in the package structure.

Changes walkthrough

Relevant files                                                                                                                                 
Enhancement
networkpolicy.go                                                                                       
    pkg/apis/softwarecomposition/v1beta1/networkpolicy/networkpolicy.go

    The GenerateNetworkPolicy function has been refactored to
    use the v1beta1 version of NetworkNeighbors and
    KnownServer. The function now converts these objects to
    their v1 counterparts, generates the network policy using
    the v1 objects, and then converts the generated policy
    back to v1beta1. The function
    convertGeneratedNetworkPolicy, convertNetworkNeighbors,
    and convertKnownServersList are added to handle these
    conversions.

 +34/-414
Tests
generatednetworkpolicy_test.go                                                           
    pkg/registry/file/generatednetworkpolicy_test.go

    The test TestGeneratedNetworkPolicyStorage_Get has been
    updated to reflect the changes in the
    GeneratedNetworkPolicy object. The APIVersion has been
    updated from spdx.softwarecomposition.kubescape.io/v1beta1
    to spdx.softwarecomposition.kubescape.io.

 +4/-3
Miscellaneous
generatednetworkpolicy.go                                                                     
    pkg/registry/file/generatednetworkpolicy.go

    The import paths for softwarecomposition and
    networkpolicy have been updated to reflect the changes in
    the package structure.

 +2/-2
✨ Usage guide:

Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. 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 describe tool (pr_description section), use the following template:

/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:

[pr_description]
some_config1=...
some_config2=...
Enabling\disabling automation
  • When you first install the app, the default mode for the describe tool is:
pr_commands = ["/describe --pr_description.add_original_user_description=true" 
                         "--pr_description.keep_original_user_title=true", ...]

meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.

  • Markers are an alternative way to control the generated description, to give maximal control to the user. If you set:
pr_commands = ["/describe --pr_description.use_description_markers=true", ...]

the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following:

  • type: the PR type.
  • summary: the PR summary.
  • walkthrough: the PR walkthrough.

Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

Custom labels

The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other].

If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:

  • Main topic:performance - pr_agent:The main topic of this PR is performance
  • New endpoint - pr_agent:A new endpoint was added in this PR
  • SQL query - pr_agent:A new SQL query was added in this PR
  • Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile
  • ...

The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

  • /review: Request a review of your Pull Request.
  • /describe: Update the PR title and description based on the contents of the PR.
  • /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
  • /ask <QUESTION>: Ask a question about the PR.
  • /update_changelog: Update the changelog based on the PR's contents.
  • /add_docs 💎: Generate docstring for new components introduced in the PR.
  • /generate_labels 💎: Generate labels for the PR based on the PR's contents.
  • /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

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

Assets 2
Loading

Release v0.0.53

03 Jan 09:06
@github-actions github-actions
v0.0.53
cbfa885
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v0.0.53

Type

bug_fix, enhancement

Description

  • The cleanup interval for resources is now configurable through an environment variable. If the environment variable is not set or cannot be parsed, a default value of 24 hours is used.
  • The cleanup handler's logging has been improved to include the cleanup interval when a cleanup task starts and to log deletions at the debug level.
  • The metadata loading function has been updated to also load labels from the metadata file.
  • The function to delete resources by template hash or wlid has been updated to look for the template hash in the labels instead of the annotations.
  • The list of workloads to cleanup has been reduced to only include cronjob, daemonset, deployment, job, pod, replicaset, and statefulset.

PR changes walkthrough

Relevant files                                                                                                                                 
Configuration changes
1 files
main.go                                                                                                         
    main.go

    The cleanup interval for resources is now configurable
    through an environment variable. If the environment variable
    is not set or cannot be parsed, a default value of 24 hours
    is used. The cleanup handler is updated to use the new
    configurable interval.

 +7/-1
Bug_fix
1 files
cleanup.go                                                                                                   
    pkg/cleanup/cleanup.go

    The cleanup handler's logging has been improved to include
    the cleanup interval when a cleanup task starts and to log
    deletions at the debug level. The metadata loading function
    has been updated to also load labels from the metadata file.
    The function to delete resources by template hash or wlid
    has been updated to look for the template hash in the labels
    instead of the annotations. Some unused code has been
    removed.

 +9/-6
Enhancement
1 files
discovery.go                                                                                               
    pkg/cleanup/discovery.go

    The list of workloads to cleanup has been reduced to only
    include cronjob, daemonset, deployment, job, pod,
    replicaset, and statefulset. The functions to fetch wlids
    from running workloads and to fetch instance IDs and image
    IDs and replicas from running pods have been updated to
    improve logging and remove unused code.

 +5/-20
Assets 2
Loading

Release v0.0.47

18 Dec 07:42
@github-actions github-actions
v0.0.47
a315545
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v0.0.47

Merge IP addresses by ports in generated NP

Assets 2
Loading

Release v0.0.44

11 Dec 15:42
@github-actions github-actions
v0.0.44
cb8d509
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v0.0.44

Type

Tests

Description

This PR introduces enhancements in the tests for the Vulnerability Summary Storage. The changes include:

  • Addition of new test cases for the Create function in the Vulnerability Summary Storage implementation.
  • Improvement in the structure of the test cases by adding blank lines for better readability.

PR changes walkthrough

Relevant files                                                                                                                                 
Tests
1 files
vulnerabilitysummarystorage_test.go                                                 
    pkg/registry/file/vulnerabilitysummarystorage_test.go

    The changes in this file are focused on the tests for the
    Create function in the Vulnerability Summary Storage
    implementation. New test cases have been added and the
    structure of the test cases has been improved for better
    readability.
+2/-0
___ ## User description Sorry, we do not accept changes directly against this repository. Please see CONTRIBUTING.md for information on where and how to contribute instead.
Assets 2
Loading

Release v0.0.42

10 Dec 09:14
@github-actions github-actions
v0.0.42
357764c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v0.0.42

PR Type:

Refactoring, Enhancement

PR Description:

This PR enhances the KnownServers Custom Resource Definition (CRD) to support a list of KnownServerEntry objects. The changes include:

  • Refactoring the KnownServers CRD to KnownServer which now holds a list of KnownServerEntry objects.
  • Updating the OpenAPI definitions to reflect the changes in the CRD.
  • Modifying the generateNetworkPolicy function and related functions to work with the updated CRD.
  • Updating the unit tests to validate the new functionality.

PR Main Files Walkthrough:

files:

pkg/generated/openapi/zz_generated.openapi.go: Updated the OpenAPI definitions to reflect the changes in the KnownServer CRD. This includes adding definitions for KnownServer, KnownServerEntry, and KnownServerList.
pkg/registry/file/generatednetworkpolicy.go: Updated the generateNetworkPolicy function and related functions to work with the updated KnownServer CRD. This includes changes in the function parameters and the logic to handle the new structure of KnownServer.
pkg/registry/file/generatednetworkpolicy_test.go: Updated the unit tests to validate the new functionality of KnownServer. This includes changes in the test data to reflect the new structure of KnownServer.
pkg/generated/informers/externalversions/softwarecomposition/v1beta1/interface.go: Added a KnownServerInformer to the versioned informer for the softwarecomposition API group.
pkg/apis/softwarecomposition/v1beta1/network_types.go: Updated the KnownServer type definition to include a list of KnownServerEntry objects.

User Description:

Support KnownServer CRD. This PR fixes the tests and generation of network policies according to changes made on this CRD. The main change is that the old struct held a single object on the internal list, and the new one hold a list of objects (a list of KnownServerEntry), as defined on the design doc.

There is also a new test which verifies that this new list works as expected.

Assets 2
Loading

Release v0.0.39

12 Nov 07:55
@github-actions github-actions
v0.0.39
16e5ce6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v0.0.39

PR Type:

Refactoring

PR Description:

This PR includes several changes:

  • The GenerateNetworkPolicy function has been moved to a separate package (networkpolicy) and made public.
  • Workload labels have been added to the NetworkPolicy object inside the GeneratedNetworkPolicy CRD.
  • A test has been added to check that labels are added successfully.

PR Main Files Walkthrough:

files:
  • pkg/registry/file/generatednetworkpolicy.go: The GenerateNetworkPolicy function calls have been updated to use the new package location.
  • pkg/apis/softwarecomposition/networkpolicy/networkpolicy.go: "This is a new file where the GenerateNetworkPolicy function has been moved. The function now includes the addition of workload labels to the NetworkPolicy object. It also includes the generation of ingress and egress rules for the network policy."
  • pkg/apis/softwarecomposition/networkpolicy/networkpolicy_test.go: This new file likely contains tests for the GenerateNetworkPolicy function, although the specific changes are not shown in the diff.

User Description:

  • Add workload labels to the NetworkPolicy object inside GeneratedNetworkPolicy CRD
  • Move GenerateNetworkPolicy to a separate package and make it public (as it is supposed to be used by other clients)
  • Add one test to check that labels are added succesfully
Assets 2
Loading

Release v0.0.38

06 Nov 09:40
@github-actions github-actions
v0.0.38
6ea0500
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release v0.0.38

PR Type:

Enhancement

PR Description:

This PR introduces the following changes:

  • Adds a new field 'Syscalls' to the ApplicationProfileContainer struct in both 'types.go' and 'v1beta1/types.go' files.
  • Updates the conversion functions in 'zz_generated.conversion.go' to include the new 'Syscalls' field.
  • Updates the deepcopy functions in 'zz_generated.deepcopy.go' to handle the new 'Syscalls' field.
  • Updates the schema in 'zz_generated.openapi.go' to reflect the new 'Syscalls' field.

PR Main Files Walkthrough:

files:

pkg/apis/softwarecomposition/types.go: Added 'Syscalls' field to the ApplicationProfileContainer struct.
pkg/apis/softwarecomposition/v1beta1/types.go: Added 'Syscalls' field to the ApplicationProfileContainer struct with json annotations.
pkg/apis/softwarecomposition/v1beta1/zz_generated.conversion.go: Updated conversion functions to include the new 'Syscalls' field in the ApplicationProfileContainer struct.
pkg/apis/softwarecomposition/v1beta1/zz_generated.deepcopy.go: Updated deepcopy functions to handle the new 'Syscalls' field in the ApplicationProfileContainer struct.
pkg/apis/softwarecomposition/zz_generated.deepcopy.go: Updated deepcopy functions to handle the new 'Syscalls' field in the ApplicationProfileContainer struct.
pkg/generated/openapi/zz_generated.openapi.go: Updated the schema to reflect the new 'Syscalls' field in the ApplicationProfileContainer struct.

Assets 2
Loading