Skip to content

Running atmos vendor pull using component.yaml failing #780

@joeccaulfield

Description

@joeccaulfield

Describe the Bug

After updating from v1.105.0 to v1.106.0, using a component.yaml file in the component directories no longer works as it returns an error if the vendor file or directory does not exist. Appears to be related to this change: https://github.com/cloudposse/atmos/pull/737/files#diff-35bbd3669178afb0acaaebfb4ec924ec99189338a9bc05232b4f92a53f261518L83

Expected Behavior

Running atmos vendor pull for a component containing a component.yaml file should result in the component being successfully vendored with specified mixins added.

Component config file

image

Expected command output

image

Steps to Reproduce

Running the same command using v1.106.0 results in an error due to the vendor file and/or directory not existing.

image

Screenshots

No response

Environment

  • OS: WLS2/Debian12 using Geodesic 2.8.7 & Atmos 1.106.0

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug🐛 An issue with the system

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions