Question: I have this in my `atmos.yaml` ```vendor...
# atmos
j
Question: I have this in my
atmos.yaml
Copy code
vendor:
  base_path: "./vendor"
And these files:
Copy code
vendor
├── aws
│   └── eks.yaml
└── azure
    └── aks.yaml
When I do a
atmos vendor list
, I get:
Copy code
Component        Type             Tags   Manifest  Folder
───────────────────────────────────────────────────────────────────────────────────────────────
 aks-cluster-dev  Vendor Manifest  azure  aks.yaml  components/terraform/aks-cluster-dev/atmos
 eks-cluster-dev  Vendor Manifest  aws    eks.yaml  components/terraform/eks-cluster-dev/atmos
But, when I try to pull one of them, it can’t find it:
Copy code
➜ atmos vendor pull --tags azure


   Error

   Error: no YAML configuration files found in directory 'vendor'
What am I missing here?
e
Looks right, but can you share relevant portions of your vendor config
Cc @Andriy Knysh (Cloud Posse)
j
Just 2 versions of the same ‘dummy’:
eks.yaml
Copy code
apiVersion: atmos/v1
kind: AtmosVendorConfig
metadata:
  name: eks-latest
  description: EKS deployments vendor
spec:
  sources:
    - component: "eks-cluster-dev"
      metadata:
        component: eks-cluster
      source: "github.com/ourorg/ourrepo.git?ref={{.Version}}"
      path: terraform/components/eks-cluster
      version: "atmos"
      targets:
        - "components/terraform/{{ .Component }}/{{.Version}}"
      included_paths:
        - "**/*.tf"
        - "**/*.tfvars"
        - "**/*.md"
      tags:
        - aws
aks.yaml
Copy code
apiVersion: atmos/v1
kind: AtmosVendorConfig
metadata:
  name: aks-latest
  description: AKS deployments vendor
spec:
  sources:
    - component: "aks-cluster-dev"
      metadata:
        component: aks-cluster
      source: "github.com/ourorg/ourrepo.git?ref={{.Version}}"
      path: terraform/components/eks-cluster
      version: "atmos"
      targets:
        - "components/terraform/{{ .Component }}/{{.Version}}"
      included_paths:
        - "**/*.tf"
        - "**/*.tfvars"
        - "**/*.md"
      tags:
        - azure
Atmos 1.206.2 on darwin/arm64
btw
e
Ok, will look into it and get back to you. Could have sworn we have tests for this case, but there's a chance there's a regression.
On a related note, have you seen the new source provisioning?
j
Thanks. After changing some thing (cant really replicate it), it now works. I think it has to do with the toplevel
base_path
or the
vendor.base_path
.
a
@Johan what you changed, is it related to https://atmos.tools/changelog/base-path-behavior-change ?
j
No, don’t think so. The sub-dirs (relative to
vendor.base_path
) are the troublemakers; using a flat structure works just fine.
a
if you open a GH issue with your stack config, we'll look into it
j
Thanks Andriy and Erik 👍
🙇‍♂️ 1