v1.112.1

🚀 Enhancements

Fix `vendor pull` directory creation issue @Cerebrovinny (#782)

what

• Fixed the regression where the vendor command would error if the vendor manifests file path did not exist.

why

• Previously, the atmos vendor pull command would fail with a “no such file or directory” error when the vendor manifests file path was missing

✅ When vendor.yaml exists and using -c flag:
Correctly checks if the component exists in vendor.yaml
Error if component not found in vendor.yaml

✅ When no vendor.yaml but component.yaml exists:
Proceeds without vendor configurations
Pulls from component.yaml configuration
Shows a Warning about vendor.yaml not existing

✅ When component specified but no vendor.yaml or component.yaml:
Shows vendor.yaml doesn't exist
Properly errors that component.yaml doesn't exist in the component folder

✅ When no component specified:
a. With vendor.yaml:
Attempts to process vendor.yaml
Shows appropriate error for invalid configuration

b. Without vendor.yaml:
Shows vendor.yaml doesn't exist
Provides an error message about needing to specify --component flag