aws_route limitation similar to security group limitation
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 7
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
It looks like the limitation related to security groups with ingress/egress blocks not being able to be distinguished from managed rules also affects route tables and managed routes.
We have quite a few AWS route tables where some of the rules are added via Terraform aws_route resources, but some have been manually added.
driftctl does not report any of the manually added routes.
When I look in the JSON state file, the manually added routes are present in the managed aws_route_table, and so I guess that's why driftctl can't distinguish whether those rules got there via route blocks in the aws_route_table, or via aws_route resources.
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 investigating how driftctl compares routes in AWS route tables with routes managed through Terraform aws_route resources. Reproduce the case with manually added and Terraform-managed routes, then verify that the completed behavior distinguishes those routes and reports the unmanaged ones.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, terraform
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100