Connect your code

Discovery tells you what exists. Connecting your code tells you where it came from.

What you connect

• A source control provider. Install the GitHub App, or create a GitLab connection. Aletheia reads repository contents and pull requests for the repositories you select.
• Terraform state sources. You designate the specific state locations Aletheia may read. It reads only the state objects you point it at.

You choose which repositories are in scope. Selecting fewer is always safe — Aletheia simply has less to match against.

What mapping produces

Once both sides are connected, Aletheia joins live resources against state and code. Each resource then carries:

• A management state — managed_synchronized, unmanaged, conflicting, managed_missing, or unknown.
• A confidence tier for the match: confirmed, high, medium, or low.
• The evidence behind it: which state source, which address, which identifier agreed.

You can filter the resource list by management state, which is how you find resources that exist in AWS but are declared nowhere in code.

When Aletheia gets it wrong

Mapping is inference, and inference is sometimes wrong. Any mapping can be corrected by hand. Corrections persist across rescans and are recorded as their own audit trail, so a correction is never silently reverted by the next scan.

In this section

• Connect GitHub — installing the GitHub App and choosing repositories.
• Connect GitLab — group access tokens, including self-managed instances.
• Repositories and IaC projects — how Terraform roots are found and what is recorded.
• Terraform state sources — designating what state Aletheia may read.
• Resource-to-code mapping — the management states, confidence tiers, and evidence.
• Correcting a mapping — overriding a wrong match, permanently.

Where to go next

• CI integration to record what your pipeline plans and applies.
• Explore your infrastructure to use the mapped inventory.