DevOps Community Sponsored by Cloud Posse

SweetOps

I am reviewing <https://github.com/cloudposse/atmos/tree/main/examples/demo-vendoring|atmos/examples/demo-vendoring at main · cloudposse/atmos> and trying to understand how I can improve my vendor manifest to permit developers to side-load a vendor manifest in their stack, while still maintaining the vendor manifest that I include in my service catalog

Do I need to use `vendor.d` with `imports: []`?

Or statically assign something like this?
```apiVersion: atmos/v1
kind: AtmosVendorConfig
metadata:
  name: iac-service-catalog-vendor-config
  description: |
    Atmos manifest for CFSB vendor components.
    This manifest is used to pull components from:
      1. Terraform registry
      2. CFSB Bitbucket repository
    To pull components from <https://bitbucket.org/cfsb/workspace/projects/TFM>:
      1. ATMOS_BITBUCKET_TOKEN environment variable must be set
      2. Token used for authentication must have read access
    For more information, please refer to <https://atmos.tools/cli/commands/vendor/pull/#bitbucket>.
spec:
  imports:
    - "vendor/iac-service-catalog"
    - "vendor/iac-stacks"```

and have the `vendor/iac-stacks` be an empty file/placeholder?

you need to vendor all the things that make the stack valid basically

What about <https://atmos.tools/vendor/config/imports#glob-pattern-support|Imports | atmos>?

I am trying this:
```apiVersion: atmos/v1
kind: AtmosVendorConfig
metadata:
  name: vendor-config
spec:
  imports:
    - "vendor/github"
    - "vendor/iac-service-catalog"
    - "vendor/**/*"```
But I am getting this error:
``` INFO  Vendoring from 'vendor.yaml'

   Error 

   Error: either 'spec.sources' or 'spec.imports' (or both) must be defined in the vendor config file 'vendor/**/*'```