base2Services / base2Services/cfn-vpn
overriding subnet ids with the modify command doesn't disassociate the current ones first
Open
bug
cfn-vpn
- Dominant language
- Ruby
- Stars
- 3
- Forks
- 10
- Avg merge
- 14h 4m
- Merged PRs (30d)
- 2
Description
```sh
cfn-vpn modify name --subnet-ids subnet-123 subnet-456
```
produces error
```
Duplicate subnet detected in az ap-southeast-2a (Service: AmazonEC2; Status Code: 400; Error Code: InvalidClientVpnSubnetId.DuplicateAz; Request ID: ***; Proxy: null)
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the implementation of the `cfn-vpn modify` command and trace how the supplied subnet IDs are applied to the existing Client VPN endpoint. Reproduce the command using the example IDs and verify that replacing subnets no longer produces the `DuplicateAz` error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, ruby
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100