vendor.yaml presence breaks per-component component.yaml vendoring

[jaguer0]

Atmos Version: 1.212.0 (darwin/arm64)

Summary

When a top-level vendor.yaml exists in the project root, atmos vendor pull -c <component> ignores per-component component.yaml files entirely — even if the requested component is not defined in vendor.yaml.

Expected Behavior

atmos vendor pull -c vpc should fall back to components/terraform/vpc/component.yaml when vpc is not defined as a source in vendor.yaml.

Actual Behavior

Atmos only searches vendor.yaml (and its imports) for the component name. If it's not found there, it errors out without checking for a component.yaml in the component directory:

Error: the flag '--component' is passed, but the component is not defined in
any of the 'sources' in the vendor config file and the imports component 'vpc',
file 'vendor.yaml'

Steps to Reproduce

1. Have a project with existing per-component vendoring via component.yaml files (e.g., components/terraform/vpc/component.yaml with kind: ComponentVendorConfig)

2. Add a top-level vendor.yaml for any purpose:

apiVersion: atmos/v1
kind: AtmosVendorConfig
metadata:
  name: example
spec:
  sources:
    - component: "agent-skills"
      source: "github.com/cloudposse/atmos.git//agent-skills?ref={{.Version}}"
      version: "main"
      targets:
        - "agent-skills"

3. Run: atmos vendor pull -c vpc

4. Observe the error. Removing vendor.yaml restores expected behavior.

Workaround

Remove the top-level vendor.yaml before running per-component vendor pulls.