Describe the Feature
As we make more extensive use of vendoring, especially as part of our blueprints, adding the ability to rapidly vendor all components would speed up the cold start process.
Expected Behavior
A clear and concise description of what you expected to happen.
Running the command:
If the the component folder has files other than the component.yaml and a README.md, then the vendoring would be skipped unless the --refresh flag is passed.
Running the command would cause atmos to recursively find all component.yaml files in every component folder and perform a vendor pull
A --dry-run argument would cause atmos to run through all component folders and determine where it would vendor, and where it would skip. Combining --dry-run with --refresh would result in all vendor'able folders being emitted.
Use Case
- Cold starts. Also, it would be helpful for companies that choose not to commit vendored components.
- Upgrades. Bump the version of components and fetch them all. If combined with
atmos describe affected, it would be easy to understand which components are out-of-date.
Describe Ideal Solution
A clear and concise description of what you want to happen. If you don't know, that's okay.
Alternatives Considered
We currently use workflows. Subcommands would also fit the bill.
Something like the following could also work, but this functionality would be better suited as core functionality.
(This example has not been tested)
# subcommand in atmos.yaml
commands:
- name: vendor pull all
description: This command vendors every component folder that has a component.yaml
steps:
- find components/ -type f -name 'component.yaml' | dirname | xargs atmos vendor pull {} \;
Relates to
Describe the Feature
As we make more extensive use of vendoring, especially as part of our blueprints, adding the ability to rapidly vendor all components would speed up the cold start process.
Expected Behavior
A clear and concise description of what you expected to happen.
Running the command:
If the the component folder has files other than the
component.yamland aREADME.md, then the vendoring would be skipped unless the--refreshflag is passed.Running the command would cause
atmosto recursively find allcomponent.yamlfiles in every component folder and perform avendor pullA
--dry-runargument would cause atmos to run through all component folders and determine where it would vendor, and where it would skip. Combining--dry-runwith--refreshwould result in all vendor'able folders being emitted.Use Case
atmos describe affected, it would be easy to understand which components are out-of-date.Describe Ideal Solution
A clear and concise description of what you want to happen. If you don't know, that's okay.
Alternatives Considered
We currently use workflows. Subcommands would also fit the bill.
Something like the following could also work, but this functionality would be better suited as core functionality.
(This example has not been tested)
Relates to
atmos terraform deploy $component --all#292