Skip to content

Conversation

vojindj
Copy link
Collaborator

@vojindj vojindj commented Jul 23, 2024

No description provided.

@vojindj vojindj requested review from filiptubic and Shadow649 July 23, 2024 14:07
@vojindj vojindj changed the title feat(allowed ip range) Add allowed ip range resource for both monitor and secure SP-3101 feat(allowed ip range) Add allowed ip range resource for both monitor and secure Jul 31, 2024
@vojindj vojindj changed the title feat(allowed ip range) Add allowed ip range resource for both monitor and secure feat(ip filter) Add ip filter resource for both monitor and secure Jul 31, 2024
@vojindj vojindj force-pushed the SP-3101_add_allowed_ip_range_resource branch from b6d3123 to 279f7cb Compare September 3, 2024 11:34
@vojindj vojindj marked this pull request as ready for review September 5, 2024 07:54
@vojindj vojindj force-pushed the SP-3101_add_allowed_ip_range_resource branch from 9cb65f2 to aa9fb45 Compare September 5, 2024 08:13
Copy link
Collaborator

@dbonf dbonf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I get that we are not able to test the write path of sysdig_ip_filtering_settings with enabled=true in integration tests otherwise we cut ourself out of the environment, we can live with that.

@vojindj vojindj merged commit 779e9c0 into master Sep 9, 2024
23 checks passed
@vojindj vojindj deleted the SP-3101_add_allowed_ip_range_resource branch September 9, 2024 12:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants