Vendor pull does not support double-star glob for exclusions or templating on the include/exclude list

[jamengual]

Describe the Bug

atmos vendor pull can't exclude subdirs.

If I have :

stacks/
  mystacks/
    us-east-1
     pepe1
     pepe2

and vendor yaml with :

exclude_paths:
  - "**/stacks/**/pepe2"

Atmos is not able to match the path of the subdir and it vendors all the files under pepe2 dir

it is also not possible to templatize the exclude or include paths, which is helpful when you have automated pipelines that can expose the names of dirs you want to exclude.

- "**/stacks/**/${exclude_me}"

That will be nice to have.

Atmos 1.110.0

Expected Behavior

Atmos should support regexes fully for the exclude and include paths

Steps to Reproduce

atmos vendor pull

Screenshots

No response

Environment

No response

Additional Context

No response

[osterman]

@jamengual in this example, I'm a little bit confused by this: ${exclude_me} as that's not Go templating syntax and not sure what you would be referring to.

[jamengual]

@jamengual in this example, I'm a little bit confused by this: ${exclude_me} as that's not Go templating syntax and not sure what you would be referring to.

My vendor file uses :

- source: 'git::https://x-access-token:{{env "GITHUB_TOKEN"}}@github.com/ORG/pepe-iac.git'

where the token comes from the github workflow.

supporting go-template could be even better.

[osterman]

Injecting the GitHub token is now handled automatically by atmos:

• Support GITHUB_TOKEN for HTTP Requests to github.com #912

[osterman]

We won't support regexes at this time, but we will fix double-star globs to work as expected.

excluded_paths:
- **/*.{md,txt}