Parser limitation: OIQ’s OCaml-based parser is still early-stage — it sometimes stops after matching the first supported resource instead of iterating through all in a single plan.
Pricing coverage: OIQ’s pricing maps are narrow compared to Infracost. For example:
Supported (mostly) → EC2, EBS, S3, some RDS types
Partial/No support → EKS, Lambda, ASG, networking
Design choice: OIQ is built for speed and strict local evaluation, not breadth of coverage. So it doesn’t yet “aggregate” multiple different resource types into one report.
Summary -
db_instance, eks_cluster and ec2_instance are part of 1.json plan file. oiq match command showing results for EC2 instance only. Parser limitation: OIQ’s OCaml-based parser is still early-stage — it sometimes stops after matching the first supported resource instead of iterating through all in a single plan.
Parser limitation: OIQ’s OCaml-based parser is still early-stage — it sometimes stops after matching the first supported resource instead of iterating through all in a single plan.
Pricing coverage: OIQ’s pricing maps are narrow compared to Infracost. For example:
Supported (mostly) → EC2, EBS, S3, some RDS types
Partial/No support → EKS, Lambda, ASG, networking
Design choice: OIQ is built for speed and strict local evaluation, not breadth of coverage. So it doesn’t yet “aggregate” multiple different resource types into one report.
Summary -
db_instance, eks_cluster and ec2_instance are part of 1.json plan file. oiq match command showing results for EC2 instance only. Parser limitation: OIQ’s OCaml-based parser is still early-stage — it sometimes stops after matching the first supported resource instead of iterating through all in a single plan.