Skip to main content

Atmos/YAML-Aware Terraform Registry Views

Feature Requests

Problem: We are building a component catalog on top of the Terraform Registry in Spacelift. But today’s registry view is very Terraform-centric and lacks visibility into Atmos configurations.
Request:
Add support or a toggle for surfacing Atmos-specific metadata in the registry view. For example, show component.yaml references, structure, or outputs alongside traditional Terraform inputs.
Impact: Empowers teams using Atmos to build internal catalogs and encourages modular practices aligned with IaC best practices.

Status: ❌ Rejected1 comment

Log in to comment and vote

Comments1

  • Natalia Gazda

    Team•

    Aug 5, 2025

    Thanks for the feedback, @Corey Zuares

    While we understand the value of better Atmos visibility for teams using it as a configuration layer, this request introduces significant complexity for a relatively narrow use case.Spacelift's module registry is designed to remain tool-agnostic and focused on the core Terraform/OpenTofu module experience. Adding Atmos-specific metadata display would require us to:
    - Parse and understand Atmos's YAML configuration format
    - Maintain ongoing compatibility as Atmos evolves
    - Design new UI components that might confuse users who don't use Atmos
    - Support and document a tool-specific feature

    For your component catalog needs, here are some alternatives that might help:

    **1. Use module documentation**

    - Include Atmos component references in your module descriptions and READMEs

    **2. Leverage labels**

    - Tag modules with Atmos-specific labels (e.g., atmos-component:networking) to improve discoverability

    **3. Build a lightweight integration**

    - Query both Spacelift's GraphQL API and your Atmos configurations to create a unified view in a simple web app

    **4. Use Contexts** - Store Atmos metadata as mounted files in Spacelift Contexts that can be attached to relevant stacksOur focus remains on features that benefit our broader user base across all IaC tools we support.

    While we won't be adding Atmos-specific views right now to the registry, we're always working to make our APIs more powerful so you can build the custom integrations you need. I’ll also leave it in “Gathering votes” to see weather there is more demand for that topic among our customers.