Terraform Module Inventory
Pricing
from $4.90 / 1,000 page auditeds
Terraform Module Inventory
Inventory Terraform modules, providers, resources, variables, outputs, version constraints, backend declarations, and module source references from Terraform files without running plans or touching cloud accounts.
Pricing
from $4.90 / 1,000 page auditeds
Rating
0.0
(0)
Developer
junipr
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
Store Positioning
Store title: Terraform Module Inventory
Short description: Inventory Terraform modules, providers, resources, variables, outputs, version constraints, backend declarations, and module source references from Terraform files without running plans or touching cloud accounts.
SEO title: Terraform Module Inventory — technical SEO, web, and domain audit
SEO description: Inventory Terraform modules, providers, resources, variables, outputs, version constraints, backend declarations, and module source references from Terraform files without running plans or touching cloud accounts. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.
Categories: DEVELOPER_TOOLS
Keywords: terraform, module, inventory, web/domain audit
Pay-Per-Event Pricing
This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.
- Tier: W1 — Web/domain audit
- Primary event:
page-auditedat $0.00490 base - Default max charge: $10.00
- Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount
Event set:
actor-start: base $0.00500, GOLD $0.00400. Terraform Module Inventory: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.page-audited: base $0.00490, GOLD $0.00392. Terraform Module Inventory: charged when page audited is completed. The price includes Apify platform usage; no separate usage pass-through is intended.record-extracted: base $0.00372, GOLD $0.00298. Terraform Module Inventory: charged when record extracted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.finding-emitted: base $0.00372, GOLD $0.00298. Terraform Module Inventory: charged when finding emitted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.audit-report-generated: base $0.05000, GOLD $0.04000. Terraform Module Inventory: charged when audit report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
The actor accepts actor-start before work, accepts the primary event before each dataset row, and accepts the configured report event before writing report files. If maxChargeUsd or the live PPE limit blocks a charge, the corresponding row or report is not written.
Public Task Concepts
- Extract Terraform Module rows from supplied public inputs
- Inventory Terraform Module fields across a capped sample
- Normalize Terraform Module evidence for delivery
- Flag missing Terraform Module data before delivery
- Export Terraform Module records with source URLs
Inventory Terraform modules, providers, resources, variables, outputs, version constraints, backend declarations, and module source references from Terraform files without running plans or touching cloud accounts.
What it does
- Accept raw
.tfcontent, public Terraform file URLs, repository file URLs, or bundled file inputs. - Parse Terraform/HCL-style blocks where possible.
- Inventory module, provider, resource, data source, variable, output, locals, backend, required provider, and required Terraform version blocks.
- Identify module sources, module version pins, provider constraints, and unpinned/floating source references.
- Emit normalized infrastructure inventory rows.
- Generate module map and provider summary.
What it does not do
- No
terraform plan,terraform apply, state-file access, cloud API calls, secret-value reporting, or deployability guarantee.
Input fields
Primary inputs from the locked actor spec: terraformFiles, terraformFileUrls, repositoryUrls, modulePaths, includeResources, includeDataSources, includeVariables, includeOutputs, includeProviderConstraints, includeBackendBlocks, includeWarnings, maxFiles, timeoutMs. maxChargeUsd keeps runs capped during production use.
Output fields
Dataset rows include: sourceUrl, filePath, blockType, blockName, providerName, resourceType, resourceName, moduleName, moduleSource, moduleVersion, versionConstraint, variableName, defaultValuePresent, outputName, sensitiveFlag, lineNumber, warning.
Starter example
Use examples/input.tiny.json as a small starter input. Keep the first run capped and review the dataset before increasing limits.
Public task examples
- Run Terraform Module Inventory on supplied sample data: Run Terraform Module Inventory on supplied sample data using a small bounded input.
- Generate a Terraform Module Inventory QA report: Generate a Terraform Module Inventory QA report using a small bounded input.
- Find invalid rows with Terraform Module Inventory: Find invalid rows with Terraform Module Inventory using a small bounded input.
- Create a capped local endpoint readiness check for Terraform Module Inventory: Create a capped local endpoint readiness check for Terraform Module Inventory using a small bounded input.
- Prepare Terraform Module Inventory output for downstream automation: Prepare Terraform Module Inventory output for downstream automation using a small bounded input.
Public source provenance
The starter input inventories the public terraform-aws-vpc simple example at immutable commit 3ffbd46fb1c7733e1b34d8666893280454e27436. Public tasks cover its main, version, variable, and output files without running Terraform or accessing a cloud account.
Reports
terraform-module-inventory.mdterraform-module-map.jsonterraform-provider-summary.csvterraform-resource-inventory.csvterraform-version-warnings.json
Limitations and safe use
Start with supplied-input runs, then enable live endpoints only with tight caps, domain allowlists, and no secrets in public examples.