Skip to content

Probing security-group in/egress parameter parsing#37

Open
audreyll2 wants to merge 2 commits intoproject-vera:mainfrom
audreyll2:main
Open

Probing security-group in/egress parameter parsing#37
audreyll2 wants to merge 2 commits intoproject-vera:mainfrom
audreyll2:main

Conversation

@audreyll2
Copy link
Copy Markdown

What I tested

  • create-vpc
  • create-security-group
  • authorize-security-group-ingress with simple args
  • authorize-security-group-ingress with shorthand --ip-permissions
  • authorize-security-group-ingress with file:// JSON permissions
  • authorize-security-group-egress with shorthand --ip-permissions
  • describe-security-groups after each probe

What I observed

  • The authorize path is reached.
  • GroupId is present in debug output.
  • IpPermissions.N is empty.
  • IpProtocol / FromPort / ToPort / CidrIp are not arriving with usable values.
  • The emulator returns Missing required parameter: IpPermissions.
  • Cleanup also shows a follow-up dependency-state issue for security-group deletion.

Next step

  • First make simple-form ingress parsing work.
  • Then make structured --ip-permissions parsing work.
  • Then rerun the lifecycle flows that depend on security-group rules.

What I tested

create-vpc
create-security-group
authorize-security-group-ingress with simple form
authorize-security-group-ingress with shorthand --ip-permissions
authorize-security-group-ingress with file:// JSON permissions
authorize-security-group-egress with shorthand --ip-permissions
describe-security-groups after each probe

What I observed

The security-group authorize path is being reached.
GroupId is present in the debug output.
But IpPermissions.N is empty.
IpProtocol, FromPort, ToPort, and CidrIp are also not arriving with usable values.
As a result, rule construction does not happen.
The emulator returns Missing required parameter: IpPermissions.
The cleanup path also shows a follow-up issue: the security group still reports VPC dependency state and cannot be deleted cleanly afterward.

Next step

First make the simple form work:
--protocol tcp --port 22 --cidr 0.0.0.0/0
Then make structured --ip-permissions parsing work
Then rerun the lifecycle flows that depend on security-group rules
After that, clean up the security-group dependency state on delete
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.

1 participant