Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple input files #16

Open
adamrtalbot opened this issue Jun 20, 2023 · 2 comments
Open

Support multiple input files #16

adamrtalbot opened this issue Jun 20, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@adamrtalbot
Copy link
Collaborator

We could support multiple input files, so we could define resources separately and run individual bits based on what we need (i.e., only things that have changed). Care would need to be taken about order.

script.py --options orgs.yml workspaces.yml secrets.yml credentials.yml computeenvs.yml pipelines.yml launch.yml

Then re-run :

script.py --options pipelines.yml launch.yml
@ejseqera
Copy link
Owner

I'm now wondering how to handle this because currently, with little modification, we could support this so each yaml corresponding to a tw subcommand would be run as a method of Tower() and to build the resources correctly, there would have to be some order in the individual yamls you provide.

OR...based on #25...

We define a hierarchy built-in so the order of the individual yamls doesn't matter either.

Either way, I think it would be a good idea!

@adamrtalbot
Copy link
Collaborator Author

I feel like a hierarchy makes the most sense, then you can just scoop up any YAML and combine them. So twpy *.yml would be perfectly valid.

@ejseqera ejseqera added the enhancement New feature or request label Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants