Acceptance
GIVEN I have deployed Korifi with experimental.securityGroups.enabled=true value
GIVEN I have created a security group
WHEN I list security groups via GET /v3/security_groups
THEN I get a list of existing security groups
WHEN I list security groups with a name filter via GET /v3/security_groups?names=my-sg&page=1&per_page=1
THEN I get a list containing the security group with that name
Dev notes
- We need to implement filtering by
names as this is one of the requests the CLI sends when running cf bind-running-security-group
- We need to implement filtering by
globally_enabled_staging=true as this is what staging-security-groups invokes
- We need to implement filtering by
globally_running_staging=true as this is what running-security-groups invokes
- The rest of the filters could be out of scope for this story, we could add them as a follow up one, or implement them here if trivial
- When this story is done,
security-group, security-groups, staging-security-groups and running-security-groups commands should work, so corresponding smoke tests should be added to the suite
Acceptance
GIVEN I have deployed Korifi with
experimental.securityGroups.enabled=truevalueGIVEN I have created a security group
WHEN I list security groups via
GET /v3/security_groupsTHEN I get a list of existing security groups
WHEN I list security groups with a name filter via
GET /v3/security_groups?names=my-sg&page=1&per_page=1THEN I get a list containing the security group with that name
Dev notes
namesas this is one of the requests the CLI sends when runningcf bind-running-security-groupglobally_enabled_staging=trueas this is whatstaging-security-groupsinvokesglobally_running_staging=trueas this is whatrunning-security-groupsinvokessecurity-group,security-groups,staging-security-groupsandrunning-security-groupscommands should work, so corresponding smoke tests should be added to the suite