Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

[Improvement] Pipeline Style #16

Open
guidiego opened this issue Aug 5, 2019 · 2 comments
Open

[Improvement] Pipeline Style #16

guidiego opened this issue Aug 5, 2019 · 2 comments

Comments

@guidiego
Copy link

guidiego commented Aug 5, 2019

Problems:

  • Today we look all template-dir or template-url and compile all files (includes macro's one)
  • Today we didn't have a logical sequence between compilation and if one day we need to make some complex compile or have files that depend on another file we can't throw exceptions or make nothing related to it.
  • Our templates need to have tons of logic to prevent errors about missing params to ignore a template that doesn't fulfill the requirements

Solution:

  • I want to add a -p / --pipe to kube-render this will allow user to send me what files they want to compile in a sequence
  • When I ask for a file and this one couldn't be rendered for any reason I want to throw it.
  • Improve kube-template adding docs

Usage

kube-render -t xxxx -c xxxx -p deployment service --verbose --apply

@andrewsmedina
Copy link
Contributor

In which cases the compile in a order is important?

@guidiego
Copy link
Author

guidiego commented Aug 8, 2019

@andrewsmedina I don't think that we have a case right now, that's a hypothetical question for future features. But point 1 and 2 are what I and @andersonba discuss a lot of.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants