Open liangyuanpeng opened 1 year ago
@joostvdg shared very similar thoughts with us recently.
I think it would be valuable to have a basic ytt
example in place when folks use the "local" flow.
What I want to think about is, since this like essentially a flow which requires no user input at all, would it be valuable to have this as sort of a "quick init" option exposed via a flag?
This would ideally error out if your directory already has config and generated files in it as we would not want to overwrite existing art without having context. I do agree that this is definitely something we would like to have for someone who wants to play around with the idea of what an ideal Carvel package looks like!
Another thing to think about is if we would want to call out all good things ytt
does with the boilerplate we generate. And is the example this issue calls out does it. (I think it does, but I am wondering if we could improve it)
(@joostvdg it would be super cool to hear your thoughts on this since you had a very similar thought)
Sure, let me share some thoughts:
kctrl init
, there should be a package you could directly build into a package that does something.--generate=default
, --generate=kubernetes
, --generate=disabled
something like that.generate
flag. Like --generate=<URL>
, so people can share package templates. The is also avoids people from requesting more and more things to be included in the provided "starter" templates.That's on the top of my head what I think about what would be nice with kctrl init
. I'm curious to know what you think @100mik ?
Describe the problem/challenge you have
I want to generate a template carvel package from command of kctrl package init for quickly to know carvel package.
Describe the solution you'd like
Auto generate files (from https://github.com/carvel-dev/ytt/tree/develop/examples/playground/basics/example-demo) :
defaults.yml
demo.yml
schema.yml
Anything else you would like to add:
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible" 👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.