DevOps Community Sponsored by Cloud Posse

SweetOps

Question... we are implementing <https://atmos.tools/design-patterns/version-management/folder-based-versioning#directory-structure|Versioning> for our components as well as Resource Templates. Following documentation, but expanding the versions to Semantic Versioning as shown below. Can we assume that <https://atmos.tools/quick-start/advanced/vendor-components|Vendoring> Components would also work under this Versioning schema?
```Component Versioning:

components/terraform/component-1
├── v1.0.0
│   └── tf-files.tf
└── v2.0.0
    └── tf-files.tf

Resource Template Versioning:

catalog/resource_templates/component-1
├── v1.0.0.yaml
└── v2.0.0.yaml```

&gt;  Can we assume that Vendoring Components would also work under this Versioning schema?

Only because I don't see what would not work here or what the concern would be.

<https://atmos.tools/changelog/vendor-target-version-overrides>

Also, we just released some improvements to vendoring that might make what you're trying to do even easier.