DevOps Community Sponsored by Cloud Posse

SweetOps

Hey, having an issue with metadata.component inheritance in Atmos 1.233.0.

My stack inherits an abstract with metadata.component: `lxd/talos-nodes`. describe component shows that inherited metadata, but the top-level component
remains `k8s_nodes`. During describe affected, an atmos component lookup then tries using the nonexistent components/terraform/k8s_nodes directory.

catalog entry: ```  k8s_nodes/lxd/defaults:
    metadata:
      type: abstract
      component: lxd/talos-nodes``` stack entry: ```  k8s_nodes:
    metadata:
      inherits:
        - k8s_nodes/lxd/defaults``` 
Setting metadata.component explicitly on the stack entry fixes it...

is this intended behaviour?

Was able to reproduce it. In looking for when it started, it appears that it's been a bug since the introduction of  "metadata" inheritance. We'll get this fixed in 1.234.0

<https://github.com/cloudposse/atmos/pull/3508|github.com/cloudposse/atmos/pull/3508>

awesome, thanks for looking into that for me!