Describe the Bug

I upgraded Atmos from version 1.180.0 to 1.190.0 (latest at the moment). After the upgrade, I noticed some unexpected behavior when running atmos vendor pull. It may be a mistake on my side or something I overlooked in the update notes, but the behavior differs from the previous version.

With the following vendor configuration file, Atmos 1.180.0 correctly reads the vendor declaration, generates the Terraform root component in the specified directory, and includes the expected contents. However, in 1.190.0, only the directory gets created, and it remains empty without any of the contents that should be included.

When I set the atmos log level to debug, I see warnings about glob expression matching, but I don’t fully understand what they mean.

Slack Conversation

Expected Behavior

Atmos correctly reads the vendor declaration, generates the Terraform root component in the specified directory, and includes the expected contents.

Steps to Reproduce

Use bellow yaml and run command atmos vendor pull

apiVersion: atmos/v1
kind: AtmosVendorConfig
metadata:
  name: vendor-config
  description: Atmos terraform component vendoring manifest
spec:
  imports: []
  sources:
    - component: s3-bucket
      source: github.com/terraform-aws-modules/terraform-aws-s3-bucket.git///?ref={{.Version}}
      version: v5.7.0
      targets: ["components/terraform/s3-bucket"]
      included_paths:
        - "**/modules/**"
        - "**/*.tf"
        - "**/README.md"
        - "**/CHANGELOG.md"
        - "**/LICENSE"
      tags:
        - aws
        - storage

Screenshots

No response

Environment

No response

Additional Context

No response