redhat-developer / redhat-developer/mapt
feat(aws): Support for using fixed VPCs
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
Currently we deploy the whole infra for AWS, under certain conditions we may need to deploy machines using an existing VPC. This implementation may find out caveats:
- If VPC is set and spot is set we will only look for spot in AZs which has subnet available for the VPC.
- Airgap will not be supported.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the AWS infrastructure deployment path and how VPC, subnet, availability-zone, and spot-instance choices are represented. Verify the behavior for an existing VPC, including limiting spot searches to AZs with available subnets, and confirm that airgap remains unsupported; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100