Allow component.yaml arguments for `atmos vendor pull`

[nitrocode]

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Describe the Feature

Can we make the atmos vendor pull -c ecr take a path to put the component ?

e.g. for component

atmos vendor pull ecr \
  --path components/terraform \
  --repo-uri "github.com/cloudposse/terraform-aws-components.git//modules/ecr"

e.g. for stacks

atmos vendor pull ecr \
  --path stacks/catalog/ecr \
  --repo-uri "github.com/cloudposse/terraform-aws-components.git//stacks/catalog/ecr"

[osterman]

@nitrocode can you expand on the use-case? If using the command line arguments, would it generate a component.yaml?

[nitrocode]

The use-case is if components/terraform is not the directory where devs want to put the component. If they want to put it in components/terraform/aws for instance, they would have to do an atmos vendor pull -c ecr and then mv components/terraform/ecr components/terraform/aws/ecr