terracognita mit Homebrew, Nix installieren

Projektlinks

• Homepage
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• terracognita

Projektgeschichte

The repository was created in February 2019. In the README, Cycloid explains that infrastructure as code was part of the company's practice and that TerraCognita was built to help customers convert existing cloud infrastructure into Terraform code automatically, relying on community Terraform providers.

Early releases expanded the importer beyond its initial AWS-oriented base. Release notes show v0.3.0 adding multiple Google resources, v0.4.0 adding AzureRM support and targeted import, and v0.6.0 adding AWS profile/config support, session-token authentication, interpolation controls, HCL2 work, and Homebrew support.

Later development focused on keeping pace with provider APIs and larger resource catalogs. The changelog documents broad Azure additions, Terraform 1.1.9 and provider updates in the 0.7.x line, vSphere support and many GCP/AWS resources in v0.8.0, and AzureRM fixes and additions through v0.8.4.

Adoptionsgeschichte

The README documents binary releases, source builds, AUR packages, Homebrew installation, and Docker usage through the `cycloid/terracognita` image. It also describes InfraImport inside Cycloid as the visual representation of TerraCognita, making the CLI both a standalone package and part of Cycloid's platform workflow.

Wie es verwendet wird

The main CLI form is `terracognita [TERRAFORM_PROVIDER] [--flags]`, where users choose a provider such as `aws`, pass provider-specific flags, and emit Terraform HCL, modules, and/or state files. The README documents include/exclude filters by Terraform resource name, module generation, Docker execution with cloud credentials passed through the environment, and follow-up `terraform init` and `terraform plan` checks.

Warum Paket-Nerds sich dafür interessieren

For infrastructure package nerds, TerraCognita is notable because it packages a moving target: it embeds assumptions about Terraform, provider versions, cloud SDK behavior, generated HCL, and state output. Package managers expose it as a single CLI, but maintainers care about the bundled provider matrix and how quickly it tracks Terraform ecosystem churn.

Zeitleiste

• 2019: GitHub repository created.
• 2019: v0.1.6 release added version reporting, CI/CD, prebuilt binaries, and automated GitHub/Docker releases.
• 2019: v0.2.0 moved TFState output to Terraform 0.12 format.
• 2020: v0.4.0 added AzureRM provider support.
• 2020: v0.6.0 added AWS profile/config support, session-token authentication, HCL2-related fixes, and Homebrew support.
• 2022: v0.8.0 added vSphere provider support and expanded AWS/GCP/Azure resource coverage.
• 2023: v0.8.4 added AzureRM resources and fixes for generated HCL maps and cyclic dependencies.

Related projects

• The README lists TerraCognita alongside Cycloid's InfraMap, which reads Terraform state or HCL to generate provider-specific graphs, and TerraCost, a Terraform-oriented cloud cost estimation CLI.
• It is adjacent to Terraform import workflows and tools that inventory existing cloud accounts before migrating to infrastructure as code.

Quellen

• https://api.github.com/repos/cycloidio/terracognita
• https://api.github.com/repos/cycloidio/terracognita/releases?per_page=100
• https://github.com/cycloidio/terracognita
• https://raw.githubusercontent.com/cycloidio/terracognita/master/CHANGELOG.md
• https://raw.githubusercontent.com/cycloidio/terracognita/master/README.md
• source_facts.package-manager