Missing Component Results in Silent Failure

[joshAtRula]

Describe the Bug

When Atmos is unable to find a component it needs to in order to pull a value from (when utilizing !terraform.output or atmos.Component function calls), it silently fails with no log output or information of any kind, and simply returns an exit code of 1.

Expected Behavior

I would expect some measure of output from the binary, indicating what failed, or why, or even a stack trace to help bring the information back to Cloudposse devs for assistance.

Steps to Reproduce

Scenario Setup: atmos w/ terraform components. Component A uses an input using the atmos.Component (or !terraform.output, doesn't matter) template function, pulling in an output from Component B.

Running a plan/output/apply all works as expected (proving happy normal state).

Then remove or comment out the references to Component B in its manifest (but leave state untouched, and the resources existing).

Attempt to apply/plan/output Component A again. Atmos will silently fail with no log output at all, even with ATMOS_LOGS_LEVEL=Trace or Debug.

Screenshots

No response

Environment

• OS: OSX
• Version: 15.3
• Atmos version: 1.160.0
• No module or component versions required

Additional Context

No response

[johnseekins-pathccm]

Similarly, if I do something as simple as

components:
  terraform:
    ec2-gha-runners: []

I get no output from atmos. I recognize this is a malformed file, but it seems like atmos validate stacks should actually tell me that instead of silently crashing.